Loading vulnerability…
CVE-2026-46572 is a heap buffer overflow vulnerability in ntfs-3g affecting the function ntfs_ib_cut_tail(). The flaw is triggered during node-split handling when the software processes maliciously crafted or corrupt NTFS index data. Improper bounds handling during manipulation of index block tail data can cause a write beyond the bounds of a heap-allocated buffer. Because ntfs-3g parses attacker-controlled NTFS filesystem metadata, a crafted NTFS image or filesystem can reach the vulnerable code path and corrupt process memory.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Heap buffer overflow vulnerability in ntfs-3g triggered by maliciously crafted or corrupt index data during a node split.
Vulnerability in the ntfs_ib_cut_tail() function in NTFS-3G that may allow root code execution via a specially crafted NTFS image.
Memory-safety vulnerability in NTFS-3G function ntfs_ib_cut_tail() that could allow root code execution via a specially crafted NTFS image.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.