CVE-2026-65637

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
9.8EG
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.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Input Validation vulnerability in Apache Tomcat due to incomplete fix for CVE-2026-32990.

This issue affects Apache Tomcat: from 11.0.20 through 11.0.24, from 10.1.53 through 10.1.57, from 9.0.115 through 9.0.120.

Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121, which fix the issue.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation0.6% × 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.6%
EPSS %ILE
45th
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 (1)

Auto-updated Oct 8, 2026
Patch available.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhattomcat2026-10-07redhat
redhatjws7-tomcat-0:11.0.21-7.redhat_00006.1.el9jws2026-10-07redhat
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

(8 across 3 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
—
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(1)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 305× 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 516 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 416 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.6% · 45th percentile
  2. 2026-10-13 06:16 UTCEG score recompute
  3. 2026-10-13 06:16 UTCVendor advisory
  4. 2026-10-13 06:15 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  6. 2026-10-12 15:46 UTCEG score recompute
  7. 2026-10-12 06:05 UTCVendor advisory
  8. 2026-10-12 06:04 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:31 UTCEG score recompute
  10. 2026-10-11 16:47 UTCEG score recompute
  11. 2026-10-11 14:08 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  14. 2026-10-10 15:18 UTCVendor advisory
  15. 2026-10-10 15:18 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-10 11:10 UTCEG score recompute
  17. 2026-10-10 11:10 UTCVendor advisory
  18. 2026-10-10 11:10 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  20. 2026-10-09 07:52 UTCVendor advisory
  21. 2026-10-09 07:52 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-09 03:42 UTCEG score recompute
  23. 2026-10-09 03:42 UTCVendor advisory
  24. 2026-10-09 03:41 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 45th percentile
Show 75 more
  1. 2026-10-08 06:14 UTCVendor advisory
  2. 2026-10-08 06:14 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-08 02:17 UTCEG score recompute
  4. 2026-10-08 02:17 UTCVendor advisory
  5. 2026-10-08 02:17 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-07 09:08 UTCVendor advisory
  8. 2026-10-07 09:08 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-07 05:05 UTCVendor advisory
  10. 2026-10-07 05:05 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-07 01:09 UTCVendor advisory
  12. 2026-10-07 01:09 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-06 20:45 UTCVendor advisory
  14. 2026-10-06 20:45 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  15. 2026-10-06 16:01 UTCEG score recompute
  16. 2026-10-06 16:01 UTCVendor advisory
  17. 2026-10-06 16:01 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-06 11:54 UTCVendor advisory
  20. 2026-10-06 11:54 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-06 07:39 UTCVendor advisory
  22. 2026-10-06 07:39 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 01:51 UTCVendor advisory
  24. 2026-10-06 01:51 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-05 20:54 UTCEG score recompute
  26. 2026-10-05 20:54 UTCVendor advisory
  27. 2026-10-05 20:54 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  28. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  29. 2026-10-05 16:58 UTCVendor advisory
  30. 2026-10-05 16:58 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-05 11:39 UTCVendor advisory
  32. 2026-10-05 11:39 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 07:42 UTCVendor advisory
  34. 2026-10-05 07:42 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-05 03:46 UTCVendor advisory
  36. 2026-10-05 03:46 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-04 23:41 UTCVendor advisory
  38. 2026-10-04 23:41 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-04 19:44 UTCVendor advisory
  40. 2026-10-04 19:44 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-04 13:57 UTCVendor advisory
  42. 2026-10-04 13:57 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-04 10:01 UTCVendor advisory
  44. 2026-10-04 10:01 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-04 06:04 UTCVendor advisory
  46. 2026-10-04 06:04 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-04 02:08 UTCVendor advisory
  48. 2026-10-04 02:08 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-03 20:13 UTCVendor advisory
  50. 2026-10-03 20:13 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-03 16:17 UTCEG score recompute
  52. 2026-10-03 16:17 UTCVendor advisory
  53. 2026-10-03 16:16 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  54. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  55. 2026-10-03 04:31 UTCVendor advisory
  56. 2026-10-03 04:31 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-03 00:34 UTCVendor advisory
  58. 2026-10-03 00:34 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-02 18:53 UTCEG score recompute
  60. 2026-10-02 18:53 UTCVendor advisory
  61. 2026-10-02 18:53 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  63. 2026-10-02 14:48 UTCVendor advisory
  64. 2026-10-02 14:48 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  65. 2026-10-02 10:21 UTCVendor advisory
  66. 2026-10-02 10:20 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-10-02 06:24 UTCVendor advisory
  68. 2026-10-02 06:24 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-10-02 01:16 UTCVendor advisory
  70. 2026-10-02 01:16 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-10-01 19:59 UTCEG score recompute
  72. 2026-10-01 19:59 UTCVendor advisory
  73. 2026-10-01 19:59 UTCGHSA enrichmentGHSA-f525-44xv-f2qj · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  75. 2026-10-01 13:26 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-65637?
CVE-2026-65637 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. Improper Input Validation vulnerability in Apache Tomcat due to incomplete fix for CVE-2026-32990. This issue affects Apache Tomcat: from 11.0.20 through 11.0.24, from 10.1.53 through 10.1.57, from 9.0.115 through 9.0.120. Users are recommended to upgrade to version 11.0.25, 10.1.58 or 9.0.121,…
When was the CVE record for CVE-2026-65637 published?
The CVE record for CVE-2026-65637 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-65637 actively exploited?
CVE-2026-65637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65637?
CVE-2026-65637 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-65637?
A fix for CVE-2026-65637 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-65637 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-65637

Explore →

Is Your Infrastructure Affected by CVE-2026-65637?

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