CVE-2026-72210

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: fix off-by-one in mapping pairs decoding bounds checks

In ntfs_mapping_pairs_decompress(), attr_end points one byte past the end of the attribute record:

attr_end = (u8 *)attr + le32_to_cpu(attr->length);

The two bounds checks validating that mapping pair data bytes fit within the attribute use strict greater-than (>), which allows a one-byte out-of-bounds read when the data extends exactly to attr_end:

b = *buf & 0xf; if (b) { if (unlikely(buf + b > attr_end)) // off-by-one goto io_error; for (deltaxcn = (s8)buf[b--]; b; b--) deltaxcn = (deltaxcn << 8) + buf[b]; }

When buf + b == attr_end, the check evaluates to false and buf[b] reads one byte past the valid attribute boundary. The same pattern appears in the LCN delta bytes check.

Fix both checks to use >= so that buf[b] at exactly attr_end is correctly rejected as out of bounds.

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 19, 2026

Advisory Details (3)

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

ntfs: fix off-by-one in mapping pairs decoding bounds checks - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs: fix off-by-one in mapping pairs decoding bounds checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/18760a74ef7c28df93726445b5595162e62ed341
generic

fs: Remove NTFS classic - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ffa8f3d30236e0ab897c30bdb01224ff1fe1c89

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

Frequently asked(5)

What is CVE-2026-72210?
CVE-2026-72210 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: fix off-by-one in mapping pairs decoding bounds checks In ntfsmappingpairsdecompress(), attrend points one byte past the end of the attribute record: attrend = (u8 *)attr + le32to_cpu(attr->length); The two bounds checks…
When was CVE-2026-72210 disclosed?
CVE-2026-72210 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72210 actively exploited?
CVE-2026-72210 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-72210?
CVE-2026-72210 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-72210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72210, 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-72210

Explore →

Is Your Infrastructure Affected by CVE-2026-72210?

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