CVE-2026-110737: vaadin · Permissive Cross-domain Security Policy with Untrusted Domains
Affects vaadinSource CVE Database V5
Not known to be exploited · CVSS 2.3 Low · fixed in 25.3.3 : update vaadin when convenient.
Data as of 27 Oct 2026, 10:57 UTC
- Patch
- Available – fixed in 25.3.3, 25.2.11, 24.10.12 +16
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vaadincom.vaadin:vaadin | Affected
| Fixed in
|
| vaadincom.vaadin:vaadin-core | Affected
| Fixed in
|
| flowcom.vaadin:flow-server | Affected
| Fixed in
|
| frameworkcom.vaadin:vaadin-server | Affected
| Fixed in
|
| frameworkcom.vaadin:vaadin-server | Affected
| Fixed in
|
| frameworkcom.vaadin:vaadin-server-mpr-jakarta | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in multiple Vaadin releases as listed. Users should upgrade to the fixed versions such as 14.14.8, 23.6.17, 24.4.26, 24.7.17, 24.9.24, 24.10.12, 25.2.11, 25.3.3, 7.7.55, and 8.32.2. Versions 10-13 and 15-22 are no longer supported and users should upgrade to the latest supported versions. No other mitigation is specified or required beyond upgrading.
Description
CVE-2026-110737 is a vulnerability in Vaadin's server push feature where the push endpoint reflects the request Origin header into the Access-Control-Allow-Origin response header and allows credentials. This permissive cross-domain policy enables any page from any origin to make cross-origin requests with the user's cookies and read the response, although reading useful data requires the push session identifier. The issue affects Vaadin Framework versions from 7.1.0 and all Flow releases since January 2015. The vulnerability does not affect applications that do not use @Push or the WebSocket transport. Multiple Vaadin versions have released fixes for this issue.