CVE-2026-65182: Apache Tomcat: Bypass longest prefix security constraint

Published Aug 25, 2026
·
Updated

Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120, from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109.

Users are recommended to upgrade to version 11.0.25, 10.1.58, 9.0.121, which fixes the issue.

Affected Software

5 affected components
Apache Tomcat>=11.0.0-M1<=11.0.24
Apache Tomcat>=10.1.0-M1<=10.1.57
Apache Tomcat>=9.0.0.M1<=9.0.120
Apache Tomcat>=8.5.0<=8.5.100
Apache Tomcat>=7.0.0<=7.0.109

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 11.0.25
  2. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 10.1.58
  3. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 9.0.121

Event History

Aug 25, 2026
CVE Published
via MITRE·09:43 PM
Data Sourced
via MITRE·09:43 PM
DescriptionWeakness
Data Sourced
via NVD·10:17 PM
DescriptionWeakness

Frequently Asked Questions

1

Which deployments are exposed to this bypass?

Deployments are exposed when their security constraints define a longer path before a more restrictive constraint for a shorter sub-path. The issue affects the listed Tomcat release ranges through 11.0.24, 10.1.57, 9.0.120, 8.5.100, and 7.0.109.

2

What configuration condition does an attacker rely on?

An attacker relies on the ordering of security constraints: a constraint for a longer path must be specified before a more restrictive constraint for a shorter sub-path. The provided information does not indicate that all default Tomcat configurations meet this condition.

3

What versions remediate the issue?

Upgrade to Apache Tomcat 11.0.25, 10.1.58, or 9.0.121. These versions are identified as fixing the issue.

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