libfuse is the reference implementation of the Linux FUSE. From version 3.18.0 to before version 3.18.2, a use-after-free vulnerability in the io_uring subsystem of libfuse allows a local attacker to crash FUSE filesystem processes and potentially execute arbitrary code. When io_uring thread creation fails due to resource exhaustion (e.g., cgroup pids.max), fuse_uring_start() frees the ring pool structure but stores the dangling pointer in the session state, leading to a use-after-free when the session shuts down. The trigger is reliable in containerized environments where cgroup pids.max limits naturally constrain thread creation. This issue has been patched in version 3.18.2.
Security readout for executives and security teams
Plain-English summary
CVE-2026-33150 affects libfuse 3.18.0 and 3.18.1. A local attacker can cause FUSE filesystem processes to crash and may be able to execute code. The issue is most concerning where containers or cgroup limits make thread creation failures more likely. libfuse 3.18.2 contains the patch.
Executive priority
Treat this as high priority where FUSE is used in containerized Linux environments. It is local, not remote, but the impact includes service crashes and possible code execution. Patch affected libfuse versions promptly through normal Linux package channels.
Technical view
The vulnerability is a use-after-free in libfuse's io_uring subsystem. If io_uring thread creation fails, fuse_uring_start() frees the ring pool but leaves a dangling pointer in session state. Shutdown later reuses that pointer, causing a crash and potential arbitrary code execution.
Likely exposure
Exposure is limited to systems using libfuse versions 3.18.0 through before 3.18.2. Risk is higher for workloads running FUSE filesystems inside containers or cgroup-constrained environments, especially where pids.max can restrict thread creation.
Exploitation context
The source bundle describes local, low-privilege exploitation with no user interaction. It states the trigger is reliable in containerized environments with constrained thread creation. KEV is false, and the provided sources do not claim active exploitation in the wild.
Researcher notes
Evidence supports a narrow version range and a specific io_uring cleanup bug. The patch is linked upstream. The bundle does not provide proof of active exploitation, affected downstream package names, or a universal mitigation beyond upgrading and following vendor guidance.
Mitigation direction
Upgrade libfuse to version 3.18.2 or later.
Check vendor advisories for distribution-specific fixed packages.
Prioritize container hosts and workloads using FUSE filesystems.
Review appliances or images that bundle libfuse independently.
Track Red Hat and upstream libfuse guidance for package status.
Validation and detection
Inventory libfuse versions across hosts, containers, and base images.
Flag libfuse 3.18.0 and 3.18.1 as affected.
Identify FUSE filesystem processes using libfuse in production.
Check containerized FUSE workloads for cgroup pid constraints.
Confirm patched package versions after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Expired Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.