CVE-2026-43512

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 33% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.3%CVSS: 9.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

DEPRECATED: Authentication Bypass Issues vulnerability in digest authentication in Apache Tomcat.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 8.5.0 through 8.5.100, from before 7.0.0. Older unsupported versions any also be affect

Users are recommended to upgrade to version 11.0.22, 10.1.55 or 9.0.118 which fix the issue.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
1.3%
EPSS %ILE
70th
KEV
Not listed

Published

May 12, 2026

Last Modified

May 15, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available.
generic

oss-security - CVE-2026-43512: Apache Tomcat: Digest authenticator will authenticate any unknown user

http://www.openwall.com/lists/oss-security/2026/05/12/8
generic

Pony Mail

https://lists.apache.org/thread/7x09x7o12solvclslw3sz0288xc8wx73

Vendor Advisories for CVE-2026-43512(18)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat10-user (10.1.40-1ubuntu1.26.04.1) @ resolute2026-08-23ubuntu
ubuntutomcat7-user (7.0.52-1ubuntu0.16+esm2) @ trusty2026-08-23ubuntu
redhatjws6-tomcat-0:10.1.49-15.redhat_00013.1.el9jws2026-07-22redhat
redhattomcat-coyote2026-07-22redhat
redhatjws7-tomcat-0:11.0.21-5.redhat_00004.1.el9jws2026-07-14redhat
redhatdevspaces/server-rhel9:17806949942026-06-10redhat
redhattomcat10-main-10.1.55-1.hum12026-05-12redhat
redhattomcat11-main-11.0.22-0.1.hum12026-05-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 5 ecosystems)
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb12u1 (8 versions)
  • every version up to 10.1.55-1~deb13u1: fixed in 10.1.55-1~deb13u1
—
tomcat1111.0.11-1 ... 11.0.6-1 (6 versions)
  • every version up to 11.0.22-1~deb13u1: fixed in 11.0.22-1~deb13u1
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb13u1 (9 versions)
  • every version up to 10.1.55-1: fixed in 10.1.55-1
—
tomcat1111.0.11-1 ... 11.0.6-1 (7 versions)
  • every version up to 11.0.22-1: fixed in 11.0.22-1
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Maven(3)
PackageVulnerable rangeFix by version rangeDependents
org.apache.tomcat.embed:tomcat-embed-core11.0.0 ... 11.0.9 (42 versions)
  • every version up to 9.0.118: fixed in 9.0.118
  • 10.1.0-M1 up to 10.1.55: fixed in 10.1.55
  • 11.0.0-M1 up to 11.0.22: fixed in 11.0.22
—
org.apache.tomcat:tomcat11.0.0 ... 11.0.9 (42 versions)
  • every version up to 9.0.118: fixed in 9.0.118
  • 10.1.0-M1 up to 10.1.55: fixed in 10.1.55
  • 11.0.0-M1 up to 11.0.22: fixed in 11.0.22
—
org.apache.tomcat:tomcat-catalina11.0.0 ... 11.0.9 (42 versions)
  • every version up to 9.0.118: fixed in 9.0.118
  • 10.1.0-M1 up to 10.1.55: fixed in 10.1.55
  • 11.0.0-M1 up to 11.0.22: fixed in 11.0.22
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.10-1 ... 10.1.9-1 (33 versions)
  • every version up to 10.1.55-1~deb12u1: fixed in 10.1.55-1~deb12u1
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
tomcat99.0.107-0+deb11u1 ... 9.0.95-1 (34 versions)
  • every version up to 9.0.118-0+deb11u1: fixed in 9.0.118-0+deb11u1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 301 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-30 06:28 UTCOSV refresh
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-23 17:53 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-17 19:31 UTCEPSS rescore
  17. 2026-09-16 14:08 UTCEPSS rescore
  18. 2026-09-16 05:15 UTCEPSS rescore
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-12 15:01 UTCEPSS rescore
  21. 2026-09-11 14:53 UTCEPSS rescore
  22. 2026-09-11 11:23 UTCOSV refresh
  23. 2026-09-11 09:37 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-08 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-02 14:12 UTCEPSS rescore
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-08-30 19:17 UTCEPSS rescore
  7. 2026-08-30 01:22 UTCEPSS rescore
  8. 2026-08-28 21:41 UTCEPSS rescore
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-25 13:49 UTCEPSS rescore
  12. 2026-08-23 18:22 UTCEG score recompute
  13. 2026-08-23 18:22 UTCVendor advisory
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 10:54 UTCEG score recompute
  21. 2026-08-17 10:54 UTCVendor advisory
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 08:34 UTCVendor advisory
  24. 2026-08-16 04:17 UTCEG score recompute
  25. 2026-08-16 04:17 UTCVendor advisory
  26. 2026-08-16 02:14 UTCEPSS rescore
  27. 2026-08-15 01:30 UTCEPSS rescore
  28. 2026-08-15 00:15 UTCVendor advisory
  29. 2026-08-14 19:58 UTCVendor advisory
  30. 2026-08-14 15:40 UTCVendor advisory
  31. 2026-08-14 11:23 UTCVendor advisory
  32. 2026-08-14 07:05 UTCVendor advisory
  33. 2026-08-14 02:48 UTCEG score recompute
  34. 2026-08-14 02:48 UTCVendor advisory
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-13 10:48 UTCVendor advisory
  37. 2026-08-13 05:56 UTCVendor advisory
  38. 2026-08-13 00:51 UTCVendor advisory
  39. 2026-08-12 20:34 UTCVendor advisory
  40. 2026-08-12 16:16 UTCEG score recompute
  41. 2026-08-12 16:16 UTCVendor advisory
  42. 2026-08-12 13:51 UTCEPSS rescore
  43. 2026-08-12 00:28 UTCVendor advisory
  44. 2026-08-11 20:07 UTCVendor advisory
  45. 2026-08-11 15:43 UTCEG score recompute
  46. 2026-08-11 15:43 UTCVendor advisory
  47. 2026-08-11 13:43 UTCEPSS rescore
  48. 2026-08-11 09:50 UTCVendor advisory
  49. 2026-08-11 05:22 UTCVendor advisory
  50. 2026-08-11 01:05 UTCEG score recompute
  51. 2026-08-11 01:05 UTCVendor advisory
  52. 2026-08-11 00:00 UTCEPSS rescore
  53. 2026-08-10 12:41 UTCVendor advisory
  54. 2026-08-10 08:17 UTCVendor advisory
  55. 2026-08-10 04:00 UTCVendor advisory
  56. 2026-08-09 23:42 UTCVendor advisory
  57. 2026-08-09 19:25 UTCVendor advisory
  58. 2026-08-09 15:07 UTCEG score recompute
  59. 2026-08-09 15:07 UTCVendor advisory
  60. 2026-08-09 13:46 UTCEPSS rescore
  61. 2026-08-09 10:50 UTCVendor advisory
  62. 2026-08-09 06:25 UTCVendor advisory
  63. 2026-08-09 02:07 UTCEG score recompute
  64. 2026-08-09 02:07 UTCVendor advisory
  65. 2026-08-08 16:37 UTCEPSS rescore
  66. 2026-08-08 14:11 UTCVendor advisory
  67. 2026-08-08 09:44 UTCVendor advisory
  68. 2026-08-08 05:26 UTCVendor advisory
  69. 2026-08-08 01:09 UTCVendor advisory
  70. 2026-08-07 20:51 UTCVendor advisory
  71. 2026-08-07 16:34 UTCEG score recompute
  72. 2026-08-07 16:34 UTCVendor advisory
  73. 2026-08-07 12:17 UTCVendor advisory
  74. 2026-08-07 07:58 UTCVendor advisory
  75. 2026-08-07 01:31 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcovepseng/cve-2026-43512-poc
    First seen Jun 8, 2026

    Exploitability PoC for CVE-2026-43512 (Apache Tomcat Digest Authentication Bypass)

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43512?
CVE-2026-43512 is a critical vulnerability published on May 12, 2026. DEPRECATED: Authentication Bypass Issues vulnerability in digest authentication in Apache Tomcat. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.21, from 10.1.0-M1 through 10.1.54, from 9.0.0.M1 through 9.0.117, from 8.5.0 through 8.5.100, from before 7.0.0. Older unsupported…
When was CVE-2026-43512 disclosed?
CVE-2026-43512 was first published on May 12, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43512 actively exploited?
CVE-2026-43512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.3% probability of exploitation in the next 30 days (70th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43512?
CVE-2026-43512 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-43512?
A fix for CVE-2026-43512 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43512 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43512

Explore →

Is Your Infrastructure Affected by CVE-2026-43512?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs