ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-110803

VaadinService.requestEnd() in Vaadin Framework 8 locks the session and then reads the v-uiId request parameter outside the block that releases the lock.

Published Oct 21, 2026 · catalog updated Oct 22, 2026 · VaadinService.requestEnd() in Vaadin Framework

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-110803. EPSS is 0.28%. Act only if a listed version of VaadinService.requestEnd() in Vaadin Framework is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (VaadinService.requestEnd() in Vaadin Framework).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.28%
Remediation
Advisory link
Affected products
package maven

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • package mavenversion unspecified

How to fix CVE-2026-110803

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-110803. EPSS is 0.28%. Act only if a listed version of VaadinService.requestEnd() in Vaadin Framework is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption; CWE-667. EPSS 0.28%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 21, 2026 · NIST NVD

    Detected

    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 foreve

  2. Oct 22, 2026 · NIST NVD

    Updated

    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 foreve

Sources

  • CVE.orgVulnerability recordCVE-2026-110803

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-110803

    30-day exploitation probability 0.28%

    first.org
  • NIST NVDVulnerability recordCVE-2026-110803

    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 relea

    nvd.nist.gov
  • Snyk Vulnerability DatabasePackage advisorySNYK-JAVA-COMVAADIN-21691526

    Improper Locking

    security.snyk.io
  • Snyk Vulnerability DatabasePackage advisorySNYK-JAVA-COMVAADIN-21691527

    Improper Locking

    security.snyk.io

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Snyk Vulnerability DatabaseOct 26, 2026
  • Snyk Vulnerability DatabaseOct 26, 2026
  • FIRST EPSSOct 23, 2026
  • NIST NVDOct 22, 2026
  • CVE.orgOct 22, 2026