CVE-2026-46572

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.4 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS
Trending — 3 sources updated this week

Also known asEUVD-2026-94358 (ENISA EUVD)Source: ENISA EUVD

7.4EG
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.1%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_ib_cut_tail() in libntfs-3g/index.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by creating a file in a specially crafted directory.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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.

The score's inputs: 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

October 7, 2026

Last Modified

October 8, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Heap buffer overflow in ntfs_ib_cut_tail() · Advisory · tuxera/ntfs-3g · GitHub

https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-wx5r-gc7w-9hhc
Web page

Releases · tuxera/ntfs-3g · GitHub

https://github.com/tuxera/ntfs-3g/releases#release-2026.7.7

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuntfs-3g-dev (1:2021.8.22-3ubuntu1.4) @ jammy2026-10-31ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ntfs-3g1:2022.10.3-1 ... 1:2026.9.28-1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ntfs-3g1:2022.10.3-5, 1:2022.10.3-5+deb13u1
  • every version up to 1:2022.10.3-5+deb13u2: fixed in 1:2022.10.3-5+deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ntfs-3g1:2022.10.3-5, 1:2026.2.25-1, 1:2026.7.7-1
  • every version up to 1:2026.7.7-2: fixed in 1:2026.7.7-2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

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 9× in last 7d / 55× 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.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  3. 2026-10-31 07:15 UTCEG score recompute
  4. 2026-10-31 07:15 UTCVendor advisory
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  11. 2026-10-25 14:25 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-24 10:13 UTCEG score recompute
  14. 2026-10-24 10:13 UTCVendor advisory
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-18 03:37 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-17 13:16 UTCEG score recompute
  24. 2026-10-17 13:16 UTCVendor advisory
  25. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 30 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-12 16:02 UTCEG score recompute
  5. 2026-10-12 03:50 UTCVendor advisory
  6. 2026-10-11 19:45 UTCEG score recompute
  7. 2026-10-11 17:00 UTCEG score recompute
  8. 2026-10-11 16:20 UTCVendor advisory
  9. 2026-10-11 14:25 UTCEG score recompute
  10. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-11 04:51 UTCEG score recompute
  12. 2026-10-11 04:51 UTCVendor advisory
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-10 17:15 UTCVendor advisory
  15. 2026-10-10 05:46 UTCEG score recompute
  16. 2026-10-10 05:46 UTCVendor advisory
  17. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-09 18:17 UTCVendor advisory
  19. 2026-10-08 19:17 UTCVendor advisory
  20. 2026-10-08 18:31 UTCEG score recompute
  21. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-08 06:50 UTCVendor advisory
  23. 2026-10-07 19:21 UTCVendor advisory
  24. 2026-10-07 19:02 UTCEG score recomputeFirst assessed: 7.4 HIGH
  25. 2026-10-07 19:02 UTCVendor advisory
  26. 2026-10-07 19:01 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  27. 2026-10-07 14:49 UTCVendor advisory
  28. 2026-10-07 14:26 UTCNVD update
  29. 2026-10-07 14:01 UTCEG score recompute
  30. 2026-10-07 14:01 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-46572?
CVE-2026-46572 is a high-severity vulnerability; its CVE record was published on October 7, 2026. In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_ib_cut_tail() in libntfs-3g/index.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by creating a file in a specially crafted directory.
When was the CVE record for CVE-2026-46572 published?
The CVE record for CVE-2026-46572 was published on October 7, 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-46572 actively exploited?
CVE-2026-46572 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46572?
CVE-2026-46572 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-46572?
A fix for CVE-2026-46572 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46572 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-46572

Explore →

Is Your Infrastructure Affected by CVE-2026-46572?

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