CVE-2026-43515

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 1.1%, top 36% 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: cna:apache, epss
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

Improper Authorization vulnerability when multiple method constraints define an HTTP method for the same extension 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.

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

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
64%
KEV
Not listed

Published

May 12, 2026

Last Modified

June 4, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
No patch confirmed yet.
generic

oss-security - CVE-2026-43515: Apache Tomcat: Security constraints not correctly applied

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat9-user (9.0.16-3ubuntu0.18.04.2+esm8) @ bionic2026-08-23ubuntu
ubuntutomcat7-user (7.0.68-1ubuntu0.4+esm4) @ xenial2026-08-23ubuntu
ubuntutomcat11-user (11.0.18-1ubuntu0.1~esm1) @ resolute2026-08-23ubuntu
ubuntutomcat8-user (8.0.32-1ubuntu1.13+esm2) @ xenial2026-08-23ubuntu
redhattomcat-coyote2026-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
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 rangeFixed inDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb12u1 (8 versions)10.1.55-1~deb13u1
tomcat1111.0.11-1 ... 11.0.6-1 (6 versions)11.0.22-1~deb13u1
tomcat99.0.70-2
Debian:14(3)
PackageVulnerable rangeFixed inDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb13u1 (9 versions)10.1.55-1
tomcat1111.0.11-1 ... 11.0.6-1 (7 versions)11.0.22-1
tomcat99.0.70-2
Maven(3)
PackageVulnerable rangeFixed inDependents
org.apache.tomcat.embed:tomcat-embed-core11.0.0 ... 11.0.9 (42 versions)11.0.22
org.apache.tomcat:tomcat11.0.0 ... 11.0.9 (42 versions)11.0.22
org.apache.tomcat:tomcat-catalina11.0.0 ... 11.0.9 (42 versions)11.0.22
Debian:12(2)
PackageVulnerable rangeFixed inDependents
tomcat1010.1.10-1 ... 10.1.9-1 (33 versions)10.1.55-1~deb12u1
tomcat99.0.70-2
Debian:11(1)
PackageVulnerable rangeFixed inDependents
tomcat99.0.107-0+deb11u1 ... 9.0.95-1 (34 versions)9.0.118-0+deb11u1

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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 6× in last 7d / 99× 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 243 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43515?
CVE-2026-43515 is a critical vulnerability published on May 12, 2026. Improper Authorization vulnerability when multiple method constraints define an HTTP method for the same extension 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…
When was CVE-2026-43515 disclosed?
CVE-2026-43515 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43515 actively exploited?
CVE-2026-43515 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.9% of all scored CVEs.
What is the CVSS score of CVE-2026-43515?
CVE-2026-43515 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43515?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43515, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-43515?

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