CVE-2026-41293

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 1.6%, top 27% 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
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 2%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

Improper Input Validation vulnerability 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 10.0.0-M1 through 10.0.27. Older, end of support versions may also be affected.

Users are recommended to upgrade to version [FIXED_VERSION], which fixes the issue.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
60(Track)
EG Risk 60/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
Severity98% × 45%
Exploitation2% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
2%
EPSS %ILE
73%
KEV
Not listed

Published

May 12, 2026

Last Modified

May 15, 2026

Advisory Details (2)

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

oss-security - CVE-2026-41293: Apache Tomcat: HTTP/2 request headers not validated

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat10-user (10.1.16-1ubuntu0.1~esm4) @ noble2026-08-23ubuntu
ubuntutomcat11-user (11.0.18-1ubuntu0.1~esm1) @ resolute2026-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

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

(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 / 105× 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 238 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-41293?
CVE-2026-41293 is a critical vulnerability published on May 12, 2026. Improper Input Validation vulnerability 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 10.0.0-M1 through 10.0.27. Older, end of support versions may also be affected. Users are recommended to…
When was CVE-2026-41293 disclosed?
CVE-2026-41293 was first published in the National Vulnerability Database 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-41293 actively exploited?
CVE-2026-41293 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2% probability of exploitation in the next 30 days, which ranks it in the top 26.6% of all scored CVEs.
What is the CVSS score of CVE-2026-41293?
CVE-2026-41293 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-41293?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41293, 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-41293

Explore →

Is Your Infrastructure Affected by CVE-2026-41293?

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