CVE-2026-65182

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path.

This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through 10.1.57, from 9.0.0.M1 through 9.0.120, 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.25, 10.1.58, 9.0.121, which fixes the issue.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

August 27, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available.
Web page

oss-security - CVE-2026-65182: Apache Tomcat: Bypass longest prefix security constraint

http://www.openwall.com/lists/oss-security/2026/08/26/1

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhattomcat2026-10-07redhat
redhatjws7-tomcat-0:11.0.21-7.redhat_00006.1.el9jws2026-10-07redhat
redhatjws6-tomcat-0:10.1.49-16.redhat_00016.1.el9jws2026-10-01redhat
redhattomcat10-main-10.1.59-0.1.hum12026-09-03redhat
redhattomcat11-main-11.0.25-0.1.hum12026-08-18redhat

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

(11 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 (10 versions)
  • every version on: no fix on record
—
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-core7.0.0 ... 7.0.99 (76 versions)
  • 11.0.0-M1 up to 11.0.25: fixed in 11.0.25
  • 10.1.0-M1 up to 10.1.58: fixed in 10.1.58
  • 9.0.0-M1 up to 9.0.121: fixed in 9.0.121
  • 8.5.0 through 8.5.100: no fix on record
  • 7.0.0 through 7.0.109: no fix on record
—
org.apache.tomcat:tomcat7.0.100 ... 7.0.99 (52 versions)
  • 11.0.0-M1 up to 11.0.25: fixed in 11.0.25
  • 10.1.0-M1 up to 10.1.58: fixed in 10.1.58
  • 9.0.0-M1 up to 9.0.121: fixed in 9.0.121
  • 8.5.0 through 8.5.100: no fix on record
  • 7.0.0 through 7.0.109: no fix on record
—
org.apache.tomcat:tomcat-catalina7.0.0 ... 7.0.99 (76 versions)
  • 11.0.0-M1 up to 11.0.25: fixed in 11.0.25
  • 10.1.0-M1 up to 10.1.58: fixed in 10.1.58
  • 9.0.0-M1 up to 9.0.121: fixed in 9.0.121
  • 8.5.0 through 8.5.100: no fix on record
  • 7.0.0 through 7.0.109: no fix on record
—
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
—

Weakness Classification(2)

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 24× in last 7d / 180× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 329 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 229 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-65182?
CVE-2026-65182 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. Improper Access Control, Incorrect Authorization vulnerability in Apache Tomcat leads to security constraint bypass if a constraint for a longer path is specified before a more restrictive constraint for a shorter sub-path. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from…
When was the CVE record for CVE-2026-65182 published?
The CVE record for CVE-2026-65182 was published on August 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 27, 2026; the record at its source may have been updated since.
Is CVE-2026-65182 actively exploited?
CVE-2026-65182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65182?
CVE-2026-65182 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-65182?
A fix for CVE-2026-65182 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65182 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-65182

Explore →

Is Your Infrastructure Affected by CVE-2026-65182?

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