CVE-2026-43513

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 61% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Handling of Case Sensitivity vulnerability in LockOutRealm 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 7.0.0 through 7.0.109. Older unsupported versions may also be affected.

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

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

Published

May 12, 2026

Last Modified

May 15, 2026

Advisory Details (2)

Auto-updated May 14, 2026
Patch available.
generic

oss-security - CVE-2026-43513: Apache Tomcat: LockOutRealm treats user names as case-sensitive

http://www.openwall.com/lists/oss-security/2026/05/12/9
generic
https://lists.apache.org/thread/ytjcgldshj73lcnd1sh95od5hrghwogp

Vendor Advisories for CVE-2026-43513(17)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat7-user (7.0.68-1ubuntu0.4+esm4) @ xenial2026-08-23ubuntu
ubuntutomcat10-user (10.1.40-1ubuntu1.26.04.1) @ resolute2026-08-23ubuntu
redhattomcat11-main-11.0.24-0.2.hum12026-07-23redhat
redhattomcat10-main-10.1.57-3.1.hum12026-07-23redhat
redhattomcat-catalina2026-07-22redhat
redhatjws6-tomcat-0:10.1.49-15.redhat_00013.1.el9jws2026-07-22redhat
redhatjws7-tomcat-0:11.0.21-5.redhat_00004.1.el9jws2026-07-14redhat

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

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

Frequently asked(5)

What is CVE-2026-43513?
CVE-2026-43513 is a high vulnerability published on May 12, 2026. Improper Handling of Case Sensitivity vulnerability in LockOutRealm 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 7.0.0 through 7.0.109. Older unsupported versions…
When was CVE-2026-43513 disclosed?
CVE-2026-43513 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-43513 actively exploited?
CVE-2026-43513 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43513?
CVE-2026-43513 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-43513?
A fix for CVE-2026-43513 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43513 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-43513

Explore →

Is Your Infrastructure Affected by CVE-2026-43513?

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

Book a Demo →Browse All CVEs