# CVE-2026-56136: Information disclosure in n/a

> An out-of-bounds read in NTFS-3G allows attackers to disclose confidential information via a malicious NTFS image.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** AZL-97929, DEBIAN-CVE-2026-56136, GHSA-r66g-c39x-cw95, UBUNTU-CVE-2026-56136

## What is CVE-2026-56136?

CVE-2026-56136 is a medium-severity vulnerability in n/a, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-56136?

It affects 1 product.


Products: Tuxera Ntfs-3g.

## How do I fix CVE-2026-56136?

Upgrade to a fixed version.

## Is CVE-2026-56136 being exploited?

There is no known exploitation of CVE-2026-56136 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-46570](https://insights.sbomify.com/CVE-2026-46570/): Memory corruption in n/a (high 8.1)
- [CVE-2026-42616](https://insights.sbomify.com/CVE-2026-42616/): Memory corruption in n/a (high 7.8)
- [CVE-2026-46569](https://insights.sbomify.com/CVE-2026-46569/): Memory corruption in n/a (high 7.7)
- [CVE-2026-46572](https://insights.sbomify.com/CVE-2026-46572/): Memory corruption in n/a (high 7.4)
- [CVE-2026-56135](https://insights.sbomify.com/CVE-2026-56135/): Memory corruption in n/a (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56136 and fix it if it is affected.

What it is: CVE-2026-56136 is a medium-severity vulnerability in n/a, published on 24 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56136 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56136/ (Markdown: https://insights.sbomify.com/CVE-2026-56136/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56136
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56136
- OSV: https://osv.dev/vulnerability/CVE-2026-56136

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56136/
Summaries are generated and may contain mistakes; the official description above is the record.