CVE-2026-72208

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
9.8EG
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.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

ntfs: add bounds check before accessing EA entries

in ntfs_ea_lookup and ntfs_listxattr, this verifies that there is enough space in the EA entry before accessing the next_entry_offset field of the EA entry.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
No patch confirmed yet.
generic

ntfs: add bounds check before accessing EA entries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9d9925de1d8f233cc60d3dc356e12f232f97c15
generic

ntfs: add bounds check before accessing EA entries - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/937282f7d15b593d0be765fa2ced164130ec87f7

Vendor Advisories for CVE-2026-72208(1)

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

Data Freshness Timeline

(refreshed 44× in last 7d / 44× 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.

  1. 2026-08-20 13:05 UTCGHSA enrichment
  2. 2026-08-20 08:31 UTCGHSA enrichment
  3. 2026-08-20 04:10 UTCGHSA enrichment
  4. 2026-08-19 23:48 UTCGHSA enrichment
  5. 2026-08-19 19:26 UTCEG score recompute
  6. 2026-08-19 19:26 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 15:04 UTCGHSA enrichment
  9. 2026-08-19 10:43 UTCGHSA enrichment
  10. 2026-08-19 06:22 UTCGHSA enrichment
  11. 2026-08-19 02:00 UTCGHSA enrichment
  12. 2026-08-18 21:37 UTCGHSA enrichment
  13. 2026-08-18 17:02 UTCEG score recompute
  14. 2026-08-18 17:01 UTCGHSA enrichment
  15. 2026-08-18 13:49 UTCEPSS rescore
  16. 2026-08-18 13:49 UTCEPSS rescore
  17. 2026-08-18 11:47 UTCGHSA enrichment
  18. 2026-08-18 07:25 UTCEG score recompute
  19. 2026-08-18 07:25 UTCGHSA enrichment
  20. 2026-08-18 07:03 UTCEG score recompute
  21. 2026-08-18 07:03 UTCGHSA enrichment
  22. 2026-08-18 04:08 UTCGHSA enrichment
  23. 2026-08-17 23:46 UTCGHSA enrichment
  24. 2026-08-17 19:24 UTCGHSA enrichment
  25. 2026-08-17 15:03 UTCEG score recompute
Show 19 more
  1. 2026-08-17 15:03 UTCGHSA enrichment
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 10:41 UTCEG score recompute
  4. 2026-08-17 10:41 UTCGHSA enrichment
  5. 2026-08-17 06:20 UTCEG score recompute
  6. 2026-08-17 06:20 UTCGHSA enrichment
  7. 2026-08-17 05:59 UTCEG score recompute▲ 9.80
  8. 2026-08-17 05:59 UTCGHSA enrichment
  9. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  10. 2026-08-17 05:32 UTCEG score recompute
  11. 2026-08-17 05:32 UTCGHSA enrichment
  12. 2026-08-17 05:25 UTCMITRE cvelistV5
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:15 UTCEPSS rescore
  16. 2026-08-15 06:40 UTCGHSA enrichment
  17. 2026-08-15 06:23 UTCNVD update
  18. 2026-08-15 06:10 UTCEG score recompute
  19. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72208?
CVE-2026-72208 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: add bounds check before accessing EA entries in ntfsealookup and ntfs_listxattr, this verifies that there is enough space in the EA entry before accessing the nextentryoffset field of the EA entry.
When was CVE-2026-72208 disclosed?
CVE-2026-72208 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72208 actively exploited?
CVE-2026-72208 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 58.2% of all scored CVEs.
What is the CVSS score of CVE-2026-72208?
CVE-2026-72208 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72208, 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

Explore the affected products and dependency analysis for CVE-2026-72208

Explore →

Is Your Infrastructure Affected by CVE-2026-72208?

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

Start Free Scan →Browse All CVEs