CVE-2026-89613

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-09-11. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.8EG
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.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ntfs: reject invalid empty mapping pairs

Reject an attribute with empty mapping pairs if it has inconsistent highest VCN and size.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.6%
EPSS %ILE
44th
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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 11, 2026

Last Modified

September 13, 2026

Advisory Details (2)

Auto-updated Oct 11, 2026
Patch available.
Web page

ntfs: reject invalid empty mapping pairs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b0cc6dbc655e037251874b3e0dd1a760dcf29007
Web page

ntfs: reject invalid empty mapping pairs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/766062a82e1ce4087c7dc077224144dfd34b3661

Vendor Advisories for CVE-2026-89613(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 204× 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 99 of 222 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 123 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.6% · 44th percentile
  2. 2026-10-13 08:39 UTCEG score recompute
  3. 2026-10-13 08:39 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-12 14:48 UTCEG score recompute
  6. 2026-10-12 09:06 UTCEG score recompute
  7. 2026-10-12 09:05 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  8. 2026-10-11 21:07 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-11 19:15 UTCEG score recompute
  10. 2026-10-11 16:32 UTCEG score recompute
  11. 2026-10-11 16:05 UTCEG score recompute
  12. 2026-10-11 16:05 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  14. 2026-10-11 13:47 UTCEG score recompute
  15. 2026-10-11 11:40 UTCEG score recompute
  16. 2026-10-11 11:40 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-11 06:50 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-11 00:03 UTCEG score recompute
  19. 2026-10-11 00:03 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-10-10 19:38 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  22. 2026-10-10 15:02 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-10 10:13 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  24. 2026-10-10 05:47 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-10 01:22 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
Show 74 more
  1. 2026-10-09 20:57 UTCEG score recompute
  2. 2026-10-09 20:56 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  4. 2026-10-09 16:32 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-09 08:05 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  6. 2026-10-09 03:39 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-08 23:14 UTCEG score recompute
  8. 2026-10-08 23:14 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-08 08:56 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-08 04:31 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  12. 2026-10-08 00:06 UTCEG score recompute
  13. 2026-10-08 00:06 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-10-07 19:41 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  16. 2026-10-07 14:38 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-07 09:47 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  18. 2026-10-07 05:23 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-07 00:58 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  20. 2026-10-06 20:19 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-06 15:47 UTCEG score recompute
  22. 2026-10-06 15:47 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-06 10:43 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-06 06:18 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  26. 2026-10-06 01:36 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-05 20:54 UTCEG score recompute
  28. 2026-10-05 20:54 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  29. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  30. 2026-10-05 16:30 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-05 12:03 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  32. 2026-10-05 07:38 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  33. 2026-10-05 03:13 UTCEG score recompute
  34. 2026-10-05 03:13 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  35. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  36. 2026-10-04 22:27 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  37. 2026-10-04 18:02 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-04 13:22 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  39. 2026-10-04 08:58 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  40. 2026-10-04 04:33 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  41. 2026-10-04 00:09 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-03 19:13 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  43. 2026-10-03 14:48 UTCEG score recompute
  44. 2026-10-03 14:48 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  45. 2026-10-03 10:12 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-03 04:31 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  47. 2026-10-03 00:06 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  48. 2026-10-02 19:04 UTCEG score recompute
  49. 2026-10-02 19:04 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  50. 2026-10-02 14:39 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  51. 2026-10-02 10:10 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  52. 2026-10-02 05:45 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  53. 2026-10-02 00:21 UTCEG score recompute
  54. 2026-10-02 00:21 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  55. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  56. 2026-10-01 19:07 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  57. 2026-10-01 14:01 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  58. 2026-10-01 09:37 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  59. 2026-10-01 05:12 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  60. 2026-10-01 00:47 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  61. 2026-09-30 19:29 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  62. 2026-09-30 15:05 UTCEG score recompute
  63. 2026-09-30 15:05 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  64. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  65. 2026-09-30 10:40 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  66. 2026-09-30 06:07 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  67. 2026-09-30 01:43 UTCEG score recompute
  68. 2026-09-30 01:42 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  69. 2026-09-29 15:16 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  70. 2026-09-29 10:51 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  71. 2026-09-29 05:59 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  72. 2026-09-29 01:35 UTCEG score recompute
  73. 2026-09-29 01:35 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8
  74. 2026-09-28 21:11 UTCGHSA enrichmentGHSA-674g-rrmx-c6rx · GitHub severity CRITICAL · GitHub CVSS 9.8

Frequently asked(5)

What is CVE-2026-89613?
CVE-2026-89613 is a critical-severity vulnerability; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs: reject invalid empty mapping pairs Reject an attribute with empty mapping pairs if it has inconsistent highest VCN and size.
When was the CVE record for CVE-2026-89613 published?
The CVE record for CVE-2026-89613 was published on September 11, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-89613 actively exploited?
CVE-2026-89613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89613?
CVE-2026-89613 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89613?
A fix for CVE-2026-89613 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89613 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-89613

Explore →

Is Your Infrastructure Affected by CVE-2026-89613?

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

Book a Demo →Browse All CVEs