CVE-2026-68569

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; 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
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper Authentication vulnerability in Apache Tomcat meant that in some circumstances (e.g. CLIENT-CERT, SPNEGO) that a user would be authenticated even if the user did not exist in the DataSourceRealm.

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.

The following versions were EOL at the time the CVE was created but are known to be affected: from 8.5.0 through 8.5.100, from 7.0.0 through 7.0.109. Other unsupported versions may also be affected.

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

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

September 21, 2026

Advisory Details (1)

Auto-updated Aug 26, 2026
Patch available.
Web page
https://lists.apache.org/thread/8robqo76q0osxgw0b5lcwgz0hcf9h4zc

Vendor Advisories for CVE-2026-68569(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 / 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.60-0.1.hum12026-09-16redhat
redhattomcat11-main-11.0.26-0.1.hum12026-09-16redhat

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.

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 23× in last 7d / 136× 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 216 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 116 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-68569?
CVE-2026-68569 is a high-severity vulnerability; its CVE record was published on August 25, 2026. Improper Authentication vulnerability in Apache Tomcat meant that in some circumstances (e.g. CLIENT-CERT, SPNEGO) that a user would be authenticated even if the user did not exist in the DataSourceRealm. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.24, from 10.1.0-M1 through…
When was the CVE record for CVE-2026-68569 published?
The CVE record for CVE-2026-68569 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 September 21, 2026; the record at its source may have been updated since.
Is CVE-2026-68569 actively exploited?
CVE-2026-68569 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68569?
CVE-2026-68569 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-68569?
A fix for CVE-2026-68569 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68569 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-68569

Explore →

Is Your Infrastructure Affected by CVE-2026-68569?

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

Book a Demo →Browse All CVEs