CVE-2026-2742: Unauthorized session creation via reserved framework path access

Published Mar 10, 2026
·
Updated

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.

Other sources

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 you should update either to the latest 14, 23, 24, 25 version.

MITRE

Affected Software

13 affected componentsFixes available
maven/com.vaadin/vaadin>=14.0.0<=14.14.0, >=23.0.0<=23.6.6, >=24.0.0<=24.9.7, >=25.0.0<=25.0.1
maven/com.vaadin:vaadin<14.14.1
14.14.1
maven/com.vaadin:vaadin>=23.0.0<23.6.7
23.6.7
maven/com.vaadin:vaadin>=24.0.0<24.9.8
24.9.8
maven/com.vaadin:vaadin>=25.0.0<25.0.2
25.0.2
maven/com.vaadin:flow-server>=25.0.0<25.0.2
25.0.2
maven/com.vaadin:flow-server>=24.0.0<24.9.8
24.9.8
maven/com.vaadin:flow-server>=23.0.0<23.6.7
23.6.7
maven/com.vaadin:flow-server<14.14.1
14.14.1
Vaadin Vaadin>=10.0.0<14.14.1
Vaadin Vaadin>=15.0.0<23.6.7
Vaadin Vaadin>=24.0.0<24.9.8
Vaadin Vaadin>=25.0.0<25.0.2

Remediation

Information

Users of affected versions should apply the following mitigation or upgrade.

Event History

Mar 10, 2026
CVE Published
via MITRE·12:08 PM
Data Sourced
via MITRE·12:08 PM
RemedyDescriptionWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
RemedyAffected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-2742?

CVE-2026-2742 is classified as a medium severity authentication bypass vulnerability.

2

How do I fix CVE-2026-2742?

To fix CVE-2026-2742, upgrade your Vaadin application to a version that is not affected, specifically above 14.14.0, 23.6.6, 24.9.7, or 25.0.1.

3

Which versions of Vaadin are affected by CVE-2026-2742?

CVE-2026-2742 affects Vaadin versions 14.0.0 to 14.14.0, 23.0.0 to 23.6.6, 24.0.0 to 24.9.7, and 25.0.0 to 25.0.1.

4

Can CVE-2026-2742 lead to unauthorized access?

Yes, CVE-2026-2742 can potentially allow unauthorized session creation, leading to unauthorized access.

5

Is CVE-2026-2742 specific to any frameworks?

CVE-2026-2742 is specifically an issue for applications using Vaadin in conjunction with Spring Security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203