CVE-2026-72199

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: validate resident index root values on lookup

Resident $INDEX_ROOT values carry index header fields that callers consume after lookup. Some callers already validate parts of the layout before walking entries, but those checks are scattered and do not cover all root header invariants, such as entries_offset alignment and lower bound, index_length, and allocated_size consistency.

The resident root resize paths now keep these header fields consistent while the value size changes: ntfs_ir_truncate() lowers index.allocated_size before shrinking the resident value, and ntfs_ir_reparent() grows the resident value before publishing a larger root header. Lookup-time validation can therefore cover these invariants without tripping over the driver's own resize paths.

Add $INDEX_ROOT to the minimum resident value size table and validate the resident index header fields before returning the attribute from lookup. Require 8-byte aligned index header fields, a sane entries_offset, an index_length within allocated_size, allocated_size within the resident value, and enough entry space for at least an index entry header.

The shared validator already rejects non-resident records for resident-only attribute types, including $INDEX_ROOT.

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: validate resident index root values on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: validate resident index root values on lookup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bfb01dd319b6b4c3e79756de7b75ccf0b9a0a247

Vendor Advisories for CVE-2026-72199(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 50× in last 7d / 50× 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-21 04:33 UTCGHSA enrichment
  2. 2026-08-21 00:17 UTCEG score recompute
  3. 2026-08-21 00:17 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 20:02 UTCGHSA enrichment
  6. 2026-08-20 15:46 UTCGHSA enrichment
  7. 2026-08-20 11:28 UTCGHSA enrichment
  8. 2026-08-20 07:12 UTCGHSA enrichment
  9. 2026-08-20 02:57 UTCGHSA enrichment
  10. 2026-08-19 22:41 UTCGHSA enrichment
  11. 2026-08-19 18:25 UTCEG score recompute
  12. 2026-08-19 18:25 UTCGHSA enrichment
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 13:25 UTCGHSA enrichment
  15. 2026-08-19 09:06 UTCGHSA enrichment
  16. 2026-08-19 04:49 UTCGHSA enrichment
  17. 2026-08-19 00:34 UTCGHSA enrichment
  18. 2026-08-18 20:15 UTCGHSA enrichment
  19. 2026-08-18 15:57 UTCEG score recompute
  20. 2026-08-18 15:57 UTCGHSA enrichment
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-18 11:41 UTCGHSA enrichment
  24. 2026-08-18 07:25 UTCEG score recompute
  25. 2026-08-18 07:25 UTCGHSA enrichment
Show 25 more
  1. 2026-08-18 07:03 UTCEG score recompute
  2. 2026-08-18 07:03 UTCGHSA enrichment
  3. 2026-08-18 03:40 UTCGHSA enrichment
  4. 2026-08-17 23:25 UTCGHSA enrichment
  5. 2026-08-17 19:08 UTCGHSA enrichment
  6. 2026-08-17 14:51 UTCEG score recompute
  7. 2026-08-17 14:51 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 10:36 UTCEG score recompute
  10. 2026-08-17 10:36 UTCGHSA enrichment
  11. 2026-08-17 06:20 UTCEG score recompute
  12. 2026-08-17 06:20 UTCGHSA enrichment
  13. 2026-08-17 06:00 UTCEG score recompute 9.80
  14. 2026-08-17 06:00 UTCGHSA enrichment
  15. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  16. 2026-08-17 05:32 UTCEG score recompute
  17. 2026-08-17 05:32 UTCGHSA enrichment
  18. 2026-08-17 05:24 UTCMITRE cvelistV5
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:15 UTCEPSS rescore
  22. 2026-08-15 06:40 UTCGHSA enrichment
  23. 2026-08-15 06:23 UTCNVD update
  24. 2026-08-15 06:10 UTCEG score recompute
  25. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72199?
CVE-2026-72199 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: validate resident index root values on lookup Resident $INDEX_ROOT values carry index header fields that callers consume after lookup. Some callers already validate parts of the layout before walking entries, but those checks…
When was CVE-2026-72199 disclosed?
CVE-2026-72199 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-72199 actively exploited?
CVE-2026-72199 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-72199?
CVE-2026-72199 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72199, 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-72199

Explore →

Is Your Infrastructure Affected by CVE-2026-72199?

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