CVE-2026-110803
Last modified
CVE-2026-110803 is a high-severity vulnerability rated 8.7/10 on the CVSS scale. 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. EPSS estimates a 0.28% chance of exploitation in the next 30 days.
Description
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 the request exhausts the thread pool and takes the application down. No authentication is required: a session cookie, which any client obtains with a single request, is enough. Vaadin 10 and later are not affected, because Flow releases the lock in a finally block and does not read that parameter there, and Vaadin Framework 7 is not affected either. Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include: Product version Vaadin Framework 8.16.0 - 8.32.1 Mitigation Upgrade to 8.32.2 Vaadin Framework 7 and Vaadin 10 and later do not carry this behaviour and need no upgrade for this issue. Artifacts Maven coordinates / Vulnerable versions / Fixed version com.vaadin:vaadin-server / 8.16.0 - 8.32.1 / >=8.32.2 com.vaadin:vaadin-server-mpr-jakarta / 8.18.0 - 8.32.1 / >=8.32.2
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| vaadin | framework | >= 8.16.0, < 8.32.2 |
| vaadin | framework | >= 8.18.0, < 8.32.2 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-110803?
How severe is CVE-2026-110803?
How do I fix CVE-2026-110803?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-110777A flaw was found in evolution-data-server. Calendar events c…5.7
- CVE-2026-11078Inappropriate implementation in FileSystem in Google Chrome …6.5
- CVE-2026-11079Insufficient validation of untrusted input in Codecs in Goog…8.8
- CVE-2026-110799Vvveb is a powerful and easy to use CMS with page builder to…9.8
- CVE-2026-1108A security vulnerability has been detected in cijliu librtsp…7.8
- CVE-2026-11080Use after free in WebView in Google Chrome on Android prior …8.8
- CVE-2026-110804Improperly controlled modification of JIT elevation settings…4.3
- CVE-2026-110805Server-side request forgery in PingOne groups endpoint in De…2.6
- CVE-2026-110806Incorrect authorization in add-on properties in Devolutions …6.5
- CVE-2026-110807A weakness has been identified in sgl-project SGLang up to 0…4.3
- CVE-2026-110808The Essential Addons for Elementor WordPress plugin before …
- CVE-2026-110809A security vulnerability has been detected in sgl-project SG…4.3
Are you affected by CVE-2026-110803?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
