PatchTheCVECVE-2026-110803: VaadinService.requestEnd() in Vaadin Framework 8 locks the session and then reads the v-uiId request parameter
CVE-2026-110803 is a high-severity flaw (CVSS 8.7) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
VaadinService.requestEnd() in Vaadin Framework 8 locks the session and then reads the v-uiId request parameter outside the block that releases the lock. A request carrying a non-numeric v-uiId makes Integer.parseInt throw while the session lock is held, so the lock is never released and the container thread returns to its pool still owning it. Every later request to that session then blocks forever in VaadinService.lockSession(), and repeating th
Why this priority
- High severity
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-10-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-110803?
No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.
Is CVE-2026-110803 being exploited?
CVE-2026-110803 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-110803 affect?
CVE-2026-110803 affects affected software. Severity is high (CVSS 8.7). VaadinService.requestEnd() in Vaadin Framework 8 locks the session and then reads the v-uiId request parameter outside the block that releases the lock. A request carrying a non-numeric v-uiId makes Integer.parseInt throw while the session
How urgent is CVE-2026-110803?
Priority 40/100. High severity; Remotely exploitable, no login, no user action