Skip to main content
CVE-2024-52316VulnerabilityPublished Updated

CVE-2024-52316: Apache Tomcat · Unchecked Error Condition

Affects Apache TomcatSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical · fixed in 11.0.0 : patch Apache Tomcat as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
6.2% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.0.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Mavenorg.apache.tomcat/tomcatpkg:maven/org.apache.tomcat/tomcatOther threatsAffected
  • =11.0.0-M1
Fixed in–

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

AI-suggested

Organizations should immediately upgrade affected Apache Tomcat instances to versions 11.0.0, 10.1.31, or 9.0.96, which contain the fix for this vulnerability. Additionally, they must audit any custom Jakarta Authentication ServerAuthContext implementations to ensure proper exception handling and explicit setting of HTTP failure statuses during authentication errors. Implement rigorous testing of authentication modules to detect unchecked error conditions. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules to detect anomalous authentication behavior as a temporary mitigation. Limit exposure of Tomcat servers to trusted networks where possible and monitor authentication logs for unusual patterns indicative of bypass attempts. Finally, maintain an inventory of all Tomcat deployments and custom authentication components to prioritize remediation efforts effectively.

Description

Unchecked Error Condition vulnerability in Apache Tomcat. If Tomcat is configured to use a custom Jakarta Authentication (formerly JASPIC) ServerAuthContext component which may throw an exception during the authentication process without explicitly setting an HTTP status to indicate failure, the authentication may not fail, allowing the user to bypass the authentication process. There are no known Jakarta Authentication components that behave in this way. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.0-M26, from 10.1.0-M1 through 10.1.30, from 9.0.0-M1 through 9.0.95. The following versions were EOL at the time the CVE was created but are known to be affected: 8.5.0 though 8.5.100. Other EOL versions may also be affected. Users are recommended to upgrade to version 11.0.0, 10.1.31 or 9.0.96, which fix the issue.

References

Community reviews

Loading reviews…