Loading vulnerability…
CVE-2026-33179 affects libfuse, the reference implementation of Linux FUSE, in versions 3.18.0 through 3.18.1. The vulnerability is in the io_uring transport path, specifically in fuse_uring_init_queue during io_uring queue entry setup and registration. When numa_alloc_local fails, the code continues operating on NULL pointers instead of aborting cleanly, leading to a NULL pointer dereference. In addition, when fuse_uring_register_queue fails, NUMA-allocated resources are not properly freed and the function incorrectly returns success, creating a memory leak and inconsistent initialization state. The traditional /dev/fuse transport path is explicitly not affected. The issue was confirmed with AddressSanitizer and LeakSanitizer and fixed in libfuse 3.18.2.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
8 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.