Skip to main content
Public proof of conceptFix available

CVE-2024-52316

A public proof of concept exists; no exploitation attested.

  • Published2024-11-18
  • Fixed in10.1.31 · 9.0.96
  • WeaknessCWE-391 · CWE-754

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-11-1812:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-52316?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-52316?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP
Apache Tomcat
BranchAffectedFixed in
10.1≥ 10.1.0, < 10.1.3110.1.31
9.0≥ 9.0.0, < 9.0.969.0.96
11.0= 11.0.0no fix published
9.0≥ 9.0.0-M1, ≤ 9.0.95no fix published
10.1≥ 10.1.0-M1, ≤ 10.1.30no fix published
11.0≥ 11.0.0-M1, ≤ 11.0.0-M26no fix published
Debian debian linux
BranchAffectedFixed in
11.0= 11.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • RHSA-2026:68677 Red Hat Product Security9 products fixed

    Red Hat Security Advisory: tomcat security update

  • RHSA-2026:68659 Red Hat Product Security9 products fixed

    Red Hat Security Advisory: tomcat security update

  • RHSA-2026:68678 Red Hat Product Security9 products fixed

    Red Hat Security Advisory: tomcat security update

  • RHSA-2026:68679 Red Hat Product Security9 products fixed

    Red Hat Security Advisory: tomcat security update

  • RHSA-2026:68680 Red Hat Product Security18 products fixed

    Red Hat Security Advisory: tomcat security update

Full record on NVD

Fix

  1. Update Apache Tomcat to 10.1.31 · 9.0.96
  2. Vendor fix Red Hat Product Security RHSA-2026:68677 · 9 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

Advisories and patches

Detection

read 2026-10-23 19:24 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedTAM-K592/CVE-2024-52316
PoC-in-GitHub

Sources

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2024-11-18
Last Modified
2026-06-17
NVD status
Analyzed

Frequently asked questions

What is CVE-2024-52316?

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.

Is CVE-2024-52316 actively exploited?

Active exploitation of CVE-2024-52316 has not been confirmed. Its EPSS score was 6.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-52316?

CVE-2024-52316 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running Apache Tomcat? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database