CVE-2026-55276

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty authorisation constraints were not included when the effective web.xml was logged.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from 9.0.0.M1 through 9.0.118, from 8.5.0 through 8.5.100. Other versions that have reached end of support may also be affected.

Users are recommended to upgrade to version 11.0.23, 10.1.56 or 9.0.119 which fixes the issue.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
46
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.6%
EPSS %ILE
47th
KEV
Not listed

Published

June 29, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available.
generic

oss-security - CVE-2026-55276: Apache Tomcat: Logged effective web.xml is incomplete

http://www.openwall.com/lists/oss-security/2026/06/29/23

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntutomcat8-user (8.0.32-1ubuntu1.13+esm2) @ xenial2026-09-23ubuntu
redhatjws7-tomcat-0:11.0.21-6.redhat_00005.1.el9jws2026-08-05redhat
redhattomcat-catalina2026-08-05redhat
redhattomcat11-main-11.0.23-0.1.hum12026-06-29redhat
redhattomcat10-main-10.1.56-1.hum12026-06-24redhat

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

(9 across 4 ecosystems)
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.40-1 ... 10.1.60-1 (11 versions)
  • every version on: no fix on record
—
tomcat1111.0.11-1 ... 11.0.6-1 (10 versions)
  • every version on: no fix on record
—
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 (10 versions)
  • every version up to 10.1.60-1: fixed in 10.1.60-1
—
tomcat1111.0.11-1 ... 11.0.6-1 (9 versions)
  • every version up to 11.0.24-1: fixed in 11.0.24-1
—
tomcat9—
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
tomcat1010.1.10-1 ... 10.1.9-1 (37 versions)
  • every version on: no fix on record
—
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.43-1 ... 9.0.70-1 (28 versions)
  • every version up to 9.0.70-2: fixed in 9.0.70-2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 / 50× 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 664 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-55276?
CVE-2026-55276 is a critical vulnerability published on June 29, 2026. Always-Incorrect Control Flow Implementation vulnerability in Apache Tomcat meant that special roles and empty authorisation constraints were not included when the effective web.xml was logged. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.22, from 10.1.0-M1 through 10.1.55, from…
When was CVE-2026-55276 disclosed?
CVE-2026-55276 was first published on June 29, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55276 actively exploited?
CVE-2026-55276 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (47th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55276?
CVE-2026-55276 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-55276?
A fix for CVE-2026-55276 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55276 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-55276

Explore →

Is Your Infrastructure Affected by CVE-2026-55276?

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