CVE-2026-56136

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.7 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st 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
4.7EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.7Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In NTFS-3G through 2026.2.25, an out-of-bounds read exists in ntfs_ir_nill() in libntfs-3g/index.c that allows an attacker to read possibly confidential information in an ntfs-3g process by crafting a malicious NTFS image. This read operation is triggered by creation of a file with a crafted name.

CVSS v3
4.7
EG Score
4.7MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity47% × 45%
The EG Score, 4.7 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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)

Out of bounds memmove in ntfs_ir_nill() · Advisory · tuxera/ntfs-3g · GitHub

https://github.com/tuxera/ntfs-3g/security/advisories/GHSA-r66g-c39x-cw95

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

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

Frequently asked(5)

What is CVE-2026-56136?
CVE-2026-56136 is a medium-severity vulnerability; its CVE record was published on August 24, 2026. In NTFS-3G through 2026.2.25, an out-of-bounds read exists in ntfsirnill() in libntfs-3g/index.c that allows an attacker to read possibly confidential information in an ntfs-3g process by crafting a malicious NTFS image. This read operation is triggered by creation of a file with a crafted name.
When was the CVE record for CVE-2026-56136 published?
The CVE record for CVE-2026-56136 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-56136 actively exploited?
CVE-2026-56136 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56136?
CVE-2026-56136 has a CVSS v3.1 base score of 4.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-56136?
A fix for CVE-2026-56136 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56136 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-56136

Explore →

Is Your Infrastructure Affected by CVE-2026-56136?

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

Book a Demo →Browse All CVEs