{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33179 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33179 is a medium-severity vulnerability in libfuse, published on 20 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33179 and fix it if it is affected.\n\nWhat it is: CVE-2026-33179 is a medium-severity vulnerability in libfuse, published on 20 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33179 in the wild and no public exploit code.\n\nAffected product: libfuse. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33179/ (Markdown: https://insights.sbomify.com/CVE-2026-33179/index.md)","id":"CVE-2026-33179","markdown":"https://insights.sbomify.com/CVE-2026-33179/index.md","name":"CVE-2026-33179","record":{"aliases":["BELL-CVE-2026-33179","DEBIAN-CVE-2026-33179","GHSA-x669-v3mq-r358"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux FUSE library","requires_auth":"low_privilege","summary":"A local attacker can crash the FUSE daemon or exhaust resources via a NULL pointer dereference in the io_uring transport, requiring the io_uring feature to be enabled.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"libfuse","vendor":"libfuse_project"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"libfuse: NULL Pointer Dereference and Memory Leak in io_uring Queue Initialization","id":"CVE-2026-33179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"HAPI FHIR HTTP authentication leak in redirects","id":"CVE-2026-33180"},"packages":[],"prev":{"headline":"Statamic is missing authorization check on taxonomy term creation via fieldtype","id":"CVE-2026-33177"},"products":["libfuse"],"published":"2026-03-20","related":[{"cvss_score":7.8,"headline":"Use After Free in libfuse","id":"CVE-2026-33150","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":5.8,"headline":"Path traversal in n/a","id":"CVE-2010-3879","kev_date_added":null,"published":"2011-01-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-25","vendors":["libfuse"]},"summary":"A local attacker can crash the FUSE daemon or exhaust resources via a NULL pointer dereference in the io_uring transport, requiring the io_uring feature to be enabled.","url":"https://insights.sbomify.com/CVE-2026-33179/"}