Answer in brief
CVE-2026-2742 records a Unknown severity vulnerability in Vaadin Vulnerable to Authentication Bypass When Accessing the /VAADIN Endpoint Without a Trailing Slash. The current sources do not mark it as known exploited. The current feed maps com.vaadin:flow-server (maven), com.vaadin:flow-server (maven), com.vaadin:flow-server (maven), com.vaadin:flow-server (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps com.vaadin:flow-server (maven), com.vaadin:flow-server (maven), com.vaadin:flow-server (maven), com.vaadin:flow-server (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| com.vaadin:flow-servermaven | >=0 <14.14.1 | 14.14.1 |
| com.vaadin:flow-servermaven | >=23.0.0 <23.6.7 | 23.6.7 |
| com.vaadin:flow-servermaven | >=24.0.0 <24.9.8 | 24.9.8 |
| com.vaadin:flow-servermaven | >=25.0.0 <25.0.2 | 25.0.2 |
| com.vaadin:vaadinmaven | >=25.0.0 <25.0.2 | 25.0.2 |
| com.vaadin:vaadinmaven | >=24.0.0 <24.9.8 | 24.9.8 |
| com.vaadin:vaadinmaven | >=23.0.0 <23.6.7 | 23.6.7 |
| com.vaadin:vaadinmaven | >=0 <14.14.1 | 14.14.1 |
Published upstream
Mar 10, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Sep 10, 2026
An authentication bypass vulnerability exists in Vaadin 14.0.0 through 14.14.0, 23.0.0 through 23.6.6, 24.0.0 through 24.9.7 and 25.0.0 through 25.0.1, applications using Spring Security due to inconsistent path pattern matching of reserved framework paths. Accessing the /VAADIN endpoint without a trailing slash bypasses security filters, and allowing unauthenticated users to trigger framework initialization and create sessions without proper authorization. Users of affected versions using Spring Security should upgrade as follows: 14.0.0-14.14.0 upgrade to 14.14.1, 23.0.0-23.6.6 to 23.6.7, 24.0.0 - 24.9.7 to 24.9.8, and 25.0.0-25.0.1 upgrade to 25.0.2 or newer. Please note that Vaadin versions 10-13 and 15-22 are no longer supported and users should update either to the latest 14, 23, 24, 25 version.
Quoted source text, attributed separately from HOL analysis.