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
Trending — 4 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.

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.1(medium)
EG Risk
46(Track)
EG Risk 46/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

June 29, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Aug 1, 2026
No patch confirmed yet.
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
generic
https://lists.apache.org/thread/jy09xjlzn6r2qwvqoph8vcmf959yq68v

Vendor Advisories for CVE-2026-55276(5)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntutomcat8-user (8.0.32-1ubuntu1.13+esm2) @ xenial2026-08-21ubuntu
redhattomcat-catalina2026-08-05redhat
redhatjws7-tomcat-0:11.0.21-6.redhat_00005.1.el9jws2026-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 rangeFixed inDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb13u1 (10 versions)——
tomcat1111.0.11-1 ... 11.0.6-1 (10 versions)——
tomcat9—9.0.70-2—
Debian:14(3)
PackageVulnerable rangeFixed inDependents
tomcat1010.1.40-1 ... 10.1.55-1~deb13u1 (10 versions)——
tomcat1111.0.11-1 ... 11.0.6-1 (9 versions)11.0.24-1—
tomcat9—9.0.70-2—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
tomcat1010.1.10-1 ... 10.1.9-1 (36 versions)——
tomcat9—9.0.70-2—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
tomcat99.0.43-1 ... 9.0.70-1 (28 versions)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 78× in last 7d / 333× 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 545 total refreshes for this CVE.

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

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 56.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55276, 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-55276

Explore →

Is Your Infrastructure Affected by CVE-2026-55276?

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

Start Free Scan →Browse All CVEs