CVE-2026-33179 | libfuse up to 3.18.1 /dev/fuse incorrectly null pointer dereference (GHSA-x669-v3mq-r358)

VDB-352134 · CVE-2026-33179 · GHSA-X669-V3MQ-R358 LIBFUSE UP TO 3.18.1 /DEV/FUSE INCORRECTLY NULL POINTER DEREFERENCE HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.4 $0-$5k 1.52+ Summaryinfo A vulnerability was found in libfuse up to 3.18.1. It has been declared as problematic. This affects the function incorrectly of the file /dev/fuse. The manipulation results in null pointer dereference. This vulnerability is cataloged as CVE-2026-33179. The attack must be initiated from a local position. There is no exploit available. It is recommended to upgrade the affected component. Detailsinfo A vulnerability classified as problematic has been found in libfuse up to 3.18.1. Affected is the function incorrectly of the file /dev/fuse. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. CVE summarizes: libfuse is the reference implementation of the Linux FUSE. From version 3.18.0 to before version 3.18.2, a NULL pointer dereference and memory leak in fuse_uring_init_queue allows a local user to crash the FUSE daemon or cause resource exhaustion. When numa_alloc_local fails during io_uring queue entry setup, the code proceeds with NULL pointers. When fuse_uring_register_queue fails, NUMA allocations are leaked and the function incorrectly returns success. Only the io_uring transport is affected; the traditional /dev/fuse path is not affected. PoC confirmed with AddressSanitizer/LeakSanitizer. This issue has been patched in version 3.18.2. The advisory is available at github.com. This vulnerability is traded as CVE-2026-33179 since 03/17/2026. The exploitability is told to be easy. Local access is required to approach this attack. Technical details are known, but there is no available exploit. Upgrading to version 3.18.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 7beb86c09b6ec5aab14dc25256ed8a5ad18554d7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. Productinfo Name libfuse Version 3.18.0 3.18.1 License open-source Website Product: https://github.com/libfuse/libfuse/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.5 VulDB Meta Temp Score: 5.4 VulDB Base Score: 5.5 VulDB Temp Score: 5.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 5.5 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Null pointer dereference CWE: CWE-476 / CWE-404 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: libfuse 3.18.2 Patch: 7beb86c09b6ec5aab14dc25256ed8a5ad18554d7 Timelineinfo 03/17/2026 CVE reserved 03/20/2026 +3 days Advisory disclosed 03/20/2026 +0 days VulDB entry created 03/20/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: GHSA-x669-v3mq-r358 Status: Confirmed CVE: CVE-2026-33179 (🔒) GCVE (CVE): GCVE-0-2026-33179 GCVE (VulDB): GCVE-100-352134 Entryinfo Created: 03/20/2026 23:31 Changes: 03/20/2026 23:31 (68) Complete: 🔍 Cache ID: 99:AD4:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸