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

> An attacker can read confidential memory information by crafting a malicious NTFS image, affecting systems using NTFS-3G.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/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:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** AZL-106878, DEBIAN-CVE-2026-46571, GHSA-52gr-j4pv-9pjh, UBUNTU-CVE-2026-46571

## What is CVE-2026-46571?

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

### Official description

In NTFS-3G before 2026.7.7, a out-of-bounds read exists in ntfs_fix_file_name() in libntfs-3g/reparse.c that allows an attacker to read possibly confidential information in ntfs-3g process memory by crafting a malicious NTFS image. The out-of-bounds read is triggered by a readlink on a corrupted file.

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

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

It affects 1 product.


Products: Tuxera Ntfs-3g.

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

Upgrade to a fixed version.

## Is CVE-2026-46571 being exploited?

There is no known exploitation of CVE-2026-46571 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-46571 and fix it if it is affected.

What it is: CVE-2026-46571 is a medium-severity vulnerability in n/a, published on 7 Oct 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-46571 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-46571/ (Markdown: https://insights.sbomify.com/CVE-2026-46571/index.md)
```

## Sources

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

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