Technical impact
A Vaadin application that uses server push reflects the HTTP Origin header into the Access‑Control‑Allow‑Origin response header while also allowing credentials. This means a page loaded from any other origin can send an authenticated request to the push endpoint and receive the response, provided it knows the push identifier for the session. The vulnerability is a CORS misconfiguration (CWE‑346) that could be combined with a Trust‑On‑First‑Use model (CWE‑942) to expose sensitive information. It does not allow arbitrary code execution, but it does enable the reading of responses that are otherwise protected by session cookies. Applications that do not use @Push are not affected, nor is the WebSocket transport.
Affected Systems
Affected versions of Vaadin Flow, Vaadin Framework, and Vaadin (the core library) are impacted. The vulnerability exists in all releases from Vaadin 14.14.0 to 14.14.7, 23.6.0 to 23.6.16, 24.4.0 to 24.4.25, 24.5.0 to 24.5.15, 24.6.0 to 24.6.13, 24.7.0 to 24.7.16, 24.8.0 to 24.8.17, 24.9.0 to 24.9.23, 24.10.0 to 24.10.11, 25.0.0 to 25.0.13, 25.1.0 to 25.1.13, 25.2.0 to 25.2.10, and 25.3.0 to 25.3.2, as well as Vaadin Framework 7.1.0 through 7.7.54 and 8.0.0 through 8.32.1. All corresponding Maven coordinates listed in the advisory are affected.
Risk and Exploitability
The CVSS score is 2.3, indicating low overall severity, and no EPSS data is available, so exploitation probability is not quantifiable. The vulnerability is not listed in the CISA KEV catalog. The obtainability of the push identifier and the necessity of cookie authentication mean that real‑world exploitation is constrained, but an attacker could still gain access to session‑specific data if that identifier is exposed elsewhere. Overall risk is low but nonetheless mitigated by applying the official patch or work‑around.