{"id":"CVE-2026-110803","title":"Session Lock Leak on an Invalid UI Id Allows Denial of Service in Vaadin Framework 8","summary":"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 sessi…","severity":"high","cvss":8.7,"cvssVector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","cvssSource":"cna","cwe":["CWE-667","CWE-400"],"vendor":"vaadin","product":"com.vaadin:vaadin-server","affected":["com.vaadin:vaadin-server >= 8.16.0 < 8.32.2","com.vaadin:vaadin-server-mpr-jakarta >= 8.18.0 < 8.32.2"],"published":"2026-10-21","updated":"2026-10-21","sourceUpdated":"2026-10-21T18:22:59.789Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-110803","references":[{"url":"https://vaadin.com/security/cve-2026-110803"},{"url":"https://github.com/vaadin/framework/releases/tag/8.32.2"}],"tags":["cve.org"],"ingestedAt":"2026-10-21T19:10:31.400Z","slug":"CVE-2026-110803","body":"## Overview\n\nVaadinService.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.\n\n\nUsers of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:\n\nProduct version\nVaadin Framework 8.16.0 - 8.32.1\n\nMitigation\nUpgrade to 8.32.2\n\nVaadin Framework 7 and Vaadin 10 and later do not carry this behaviour and need no upgrade for this issue.\n\nArtifacts\nMaven coordinates / Vulnerable versions / Fixed version\ncom.vaadin:vaadin-server / 8.16.0 - 8.32.1 / >=8.32.2\ncom.vaadin:vaadin-server-mpr-jakarta / 8.18.0 - 8.32.1 / >=8.32.2\n\n## Affected\n\n- `com.vaadin:vaadin-server >= 8.16.0 < 8.32.2`\n- `com.vaadin:vaadin-server-mpr-jakarta >= 8.18.0 < 8.32.2`\n\n## Remediation\n\nUsers of affected versions should apply the following mitigation or upgrade.\n\n### Workarounds\n\nReject requests whose v-uiId parameter is not an integer before Vaadin handles them, by overriding VaadinServlet.service() and answering 400 for those requests. Locks that have already leaked are only released by restarting the application.","depth":"twilight","depthScore":48,"depthScoreParts":{"impact":47.8,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}