VulnerabilityPublished 29 May 2025Updated 3 Nov 2025

CVE-2025-46701: Org.apache.tomcat:tomcat catalina: Apache Tomcat - CGI security constraint bypass

Affects org.apache.tomcat:tomcat-catalinaSource GCVE Database

Compare

Authoritative record:CVE-2025-46701· High 7.3

Not known to be exploited · CVSS 7.3 High : upgrade to 9.0.105 soon.

Data as of 30 Oct 2026, 02:30 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CISA-ADP	CVSS 3.1	7.3

Patch: Available – fixed in 9.0.105, 10.1.41, 11.0.7

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.apache.tomcat:tomcat-catalina and org.apache.tomcat.embed:tomcat-embed-core to 9.0.105; org.apache.tomcat:tomcat-catalina and org.apache.tomcat.embed:tomcat-embed-core to 10.1.41; org.apache.tomcat:tomcat-catalina and org.apache.tomcat.embed:tomcat-embed-core to 11.0.7.

Affected software

Product	Affected	Fixed in
Mavenorg.apache.tomcat:tomcat-catalina	Affected >=9.0.0.M1 <9.0.105	Fixed in 9.0.105
Mavenorg.apache.tomcat:tomcat-catalina	Affected >=10.1.0-M1 <10.1.41	Fixed in 10.1.41
Mavenorg.apache.tomcat:tomcat-catalina	Affected >=11.0.0-M1 <11.0.7	Fixed in 11.0.7
Mavenorg.apache.tomcat.embed:tomcat-embed-core	Affected >=9.0.0.M1 <9.0.105	Fixed in 9.0.105
Mavenorg.apache.tomcat.embed:tomcat-embed-core	Affected >=10.1.0-M1 <10.1.41	Fixed in 10.1.41
Mavenorg.apache.tomcat.embed:tomcat-embed-core	Affected >=11.0.0-M1 <11.0.7	Fixed in 11.0.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and users are strongly recommended to upgrade to Apache Tomcat versions 8.5.101 or later, 9.0.105 or later, 10.1.41 or later, or 11.0.7 or later to remediate this vulnerability. No other mitigation steps are indicated by the vendor advisory.

Description

Apache Tomcat versions 8.5.0 through 8.5.100, 9.0.0.M1 through 9.0.104, 10.1.0-M1 through 10.1.40, and 11.0.0-M1 through 11.0.6 contain a vulnerability in the CGI servlet where improper handling of case sensitivity allows bypassing security constraints applied to the pathInfo component of a URI. This security constraint bypass is fixed in versions 8.5.101 and later, 9.0.105 and later, 10.1.41 and later, and 11.0.7 and later. The vulnerability has a medium severity with a CVSS score of 6.3.

Impact

Successful exploitation of this vulnerability allows an attacker to bypass security constraints on the CGI servlet pathInfo, potentially granting unauthorized access to restricted resources or functionality. The CVSS 4.0 base score of 6.3 indicates a medium severity impact with network attack vector, low complexity, no privileges required, no user interaction, and partial confidentiality and integrity impact.

CWE-178Improper Handling of Case Sensitivity (opens in a new tab)
Base weakness
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
Architecture and Design · Input Validation
Avoid making decisions based on names of resources (e.g. files) if those resources can have alternate names.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 02:30 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-178

Technical details

References

Community reviews

Related threats