Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-65182 – Security Constraint Bypass (Improper Access Control) – Apache Tomcat 7.0.0–7.0.109,

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-65182 is an improper access control / incorrect authorization vulnerability in Apache Tomcat’s security constraint processing. When a <security-constraint> is defined for a longer URL path before a more restrictive constraint defined for a shorter sub-path, Tomcat can apply the constraints in the wrong order, causing the more restrictive rule to be bypassed. This is a network-exploitable, unauthenticated issue rated CRITICAL (CVSS 9.1) that can expose protected resources to unauthorized users.

Technical details

  • Root cause: Tomcat’s constraint-matching logic evaluates security constraints against request paths without correctly prioritizing more restrictive sub-path constraints over less restrictive parent-path constraints.
  • Trigger condition: a deployment where a security constraint for a longer path (e.g. /admin/sensitive/) is declared before a more restrictive constraint for a shorter sub-path (e.g. /admin/) in web.xml or equivalent configuration.
  • Attack vector: network, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: unauthorized access to resources that should be protected by access-control constraints, resulting in high confidentiality and integrity impact; no availability impact.

Affected software

  • Apache Tomcat 11.0.0-M1 through 11.0.24
  • Apache Tomcat 10.1.0-M1 through 10.1.57
  • Apache Tomcat 9.0.0.M1 through 9.0.120
  • Apache Tomcat 8.5.0 through 8.5.100
  • Apache Tomcat 7.0.0 through 7.0.109

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: upgrade to Apache Tomcat 11.0.25, 10.1.58, or 9.0.121, which contain the fix.
  • Note: Tomcat 8.5.x and 7.0.x are listed as affected version ranges but are past their end-of-life support windows and no fixed release is available for these branches; organizations running these versions should migrate to a supported, patched branch (9.0.121+, 10.1.58+, or 11.0.25+).
  • If immediate patching is not possible: review and reorder <security-constraint> declarations so that constraints for shorter, more restrictive sub-paths are defined before constraints for longer parent paths, and audit access logs for unauthorized access to protected resources.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge