CVE-2026-56135

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% (3rd 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
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 through 2026.2.25, a heap-based buffer overflow exists in the function build_inherited_id() in libntfs-3g/security.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 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 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)
Severity74% × 45%
The EG Score, 7.4 of 10.
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
3rd
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 (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.

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

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (1)

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

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

https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-c9qg-fh4v-mq8r

Vendor Advisories for CVE-2026-56135(1)

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

Patch Availability(1)

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

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 19× in last 7d / 99× 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 100 of 158 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. None are among the latest 100 rows. The 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-10-12 21:26 UTCEG score recompute
  3. 2026-10-12 21:26 UTCVendor advisory
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-12 15:55 UTCEG score recompute
  6. 2026-10-11 19:38 UTCEG score recompute
  7. 2026-10-11 16:53 UTCEG score recompute
  8. 2026-10-11 14:16 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-10 13:20 UTCEG score recompute
  12. 2026-10-10 13:20 UTCVendor advisory
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-09 05:04 UTCEG score recompute
  15. 2026-10-09 05:04 UTCVendor advisory
  16. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-08 04:22 UTCEG score recompute
  18. 2026-10-08 04:22 UTCVendor advisory
  19. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-07 06:45 UTCVendor advisory
  21. 2026-10-06 19:20 UTCEG score recompute
  22. 2026-10-06 19:20 UTCVendor advisory
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-06 07:47 UTCEG score recompute
  25. 2026-10-06 07:47 UTCVendor advisory
Show 75 more
  1. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-05 17:05 UTCVendor advisory
  3. 2026-10-05 04:47 UTCEG score recompute
  4. 2026-10-05 04:47 UTCVendor advisory
  5. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-04 15:36 UTCVendor advisory
  7. 2026-10-04 04:02 UTCVendor advisory
  8. 2026-10-03 16:34 UTCEG score recompute
  9. 2026-10-03 16:34 UTCVendor advisory
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-02 20:58 UTCEG score recompute
  12. 2026-10-02 20:58 UTCVendor advisory
  13. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-02 08:34 UTCVendor advisory
  15. 2026-10-01 21:10 UTCEG score recompute
  16. 2026-10-01 21:10 UTCVendor advisory
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-01 07:44 UTCVendor advisory
  19. 2026-09-30 20:20 UTCEG score recompute
  20. 2026-09-30 20:20 UTCVendor advisory
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-09-30 07:21 UTCEG score recompute
  23. 2026-09-30 07:21 UTCVendor advisory
  24. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-29 15:20 UTCVendor advisory
  26. 2026-09-28 23:22 UTCEG score recompute
  27. 2026-09-28 23:22 UTCVendor advisory
  28. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-28 11:18 UTCVendor advisory
  30. 2026-09-27 23:54 UTCEG score recompute
  31. 2026-09-27 23:54 UTCVendor advisory
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-09-27 12:15 UTCVendor advisory
  34. 2026-09-27 00:51 UTCEG score recompute
  35. 2026-09-27 00:51 UTCVendor advisory
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-09-25 06:20 UTCVendor advisory
  38. 2026-09-24 18:55 UTCEG score recompute
  39. 2026-09-24 18:55 UTCVendor advisory
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-09-24 07:23 UTCVendor advisory
  42. 2026-09-23 19:59 UTCEG score recompute
  43. 2026-09-23 19:59 UTCVendor advisory
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  45. 2026-09-23 07:04 UTCVendor advisory
  46. 2026-09-22 19:39 UTCEG score recompute
  47. 2026-09-22 19:39 UTCVendor advisory
  48. 2026-09-22 06:30 UTCEG score recompute
  49. 2026-09-22 06:30 UTCVendor advisory
  50. 2026-09-21 19:06 UTCVendor advisory
  51. 2026-09-21 07:41 UTCEG score recompute
  52. 2026-09-21 07:41 UTCVendor advisory
  53. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  54. 2026-09-20 20:15 UTCVendor advisory
  55. 2026-09-20 08:51 UTCVendor advisory
  56. 2026-09-19 18:53 UTCVendor advisory
  57. 2026-09-19 07:28 UTCVendor advisory
  58. 2026-09-18 20:04 UTCEG score recompute
  59. 2026-09-18 20:04 UTCVendor advisory
  60. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-09-18 08:38 UTCVendor advisory
  62. 2026-09-17 21:14 UTCEG score recompute
  63. 2026-09-17 21:14 UTCVendor advisory
  64. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  65. 2026-09-17 09:01 UTCVendor advisory
  66. 2026-09-16 21:36 UTCEG score recompute
  67. 2026-09-16 21:36 UTCVendor advisory
  68. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-09-16 09:28 UTCVendor advisory
  70. 2026-09-15 21:05 UTCVendor advisory
  71. 2026-09-15 09:09 UTCEG score recompute
  72. 2026-09-15 09:09 UTCVendor advisory
  73. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-09-14 21:44 UTCVendor advisory
  75. 2026-09-14 10:20 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-56135?
CVE-2026-56135 is a high-severity vulnerability; its CVE record was published on August 24, 2026. In NTFS-3G through 2026.2.25, a heap-based buffer overflow exists in the function buildinheritedid() in libntfs-3g/security.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 crafted…
When was the CVE record for CVE-2026-56135 published?
The CVE record for CVE-2026-56135 was published on August 24, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-56135 actively exploited?
CVE-2026-56135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56135?
CVE-2026-56135 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-56135?
A fix for CVE-2026-56135 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56135 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-56135

Explore →

Is Your Infrastructure Affected by CVE-2026-56135?

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

Book a Demo →Browse All CVEs