{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3665 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3665 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3665 is a medium-severity vulnerability in xlnt-community xlnt, published on 7 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-3665 and fix it if it is affected.\n\nWhat it is: CVE-2026-3665 is a medium-severity vulnerability in xlnt-community xlnt, published on 7 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-3665 in the wild and no public exploit code.\n\nAffected product: xlnt-community xlnt. 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-3665/ (Markdown: https://insights.sbomify.com/CVE-2026-3665/index.md)","id":"CVE-2026-3665","markdown":"https://insights.sbomify.com/CVE-2026-3665/index.md","name":"CVE-2026-3665","record":{"aliases":["GHSA-f8w4-fphr-9q3w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"XLSX parsing library","requires_auth":"low_privilege","summary":"A local attacker can cause a denial of service via null pointer dereference in the xlnt library's XLSX parser.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"xlnt","vendor":"xlnt-community"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"},{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"A vulnerability was identified in xlnt-community xlnt up to 1.6.1. The affected element is the function xlnt::detail::xlsx_consumer::read_office_document of the file source/detail/serialization/xlsx_consumer.cpp of the component XLSX File Parser. The manipulation leads to null pointer dereference. The attack must be carried out locally. The exploit is publicly available and might be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"xlnt-community xlnt XLSX File xlsx_consumer.cpp read_office_document null pointer dereference","id":"CVE-2026-3665","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"wpForo Forum \u003c= 2.4.16 - Authenticated (Subscriber+) Arbitrary File Deletion via Post Body","id":"CVE-2026-3666"},"packages":[],"prev":{"headline":"xlnt-community xlnt Encrypted XLSX File compound_document.cpp read_directory out-of-bounds","id":"CVE-2026-3664"},"products":["xlnt"],"published":"2026-03-07","related":[{"cvss_score":4.8,"headline":"xlnt-community xlnt XLSX File compound_document.cpp xsgetn out-of-bounds","id":"CVE-2026-3663","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.8,"headline":"xlnt-community xlnt Encrypted XLSX File compound_document.cpp read_directory out-of-bounds","id":"CVE-2026-3664","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":4.8,"headline":"xlnt-community xlnt Compound Document binary.hpp append heap-based overflow","id":"CVE-2026-3463","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":4.8,"headline":"xlnt-community xlnt Encrypted XLSX File base64.cpp decode_base64 off-by-one","id":"CVE-2026-2703","kev_date_added":null,"published":"2026-02-19"}],"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-11","vendors":["xlnt-community"]},"summary":"A local attacker can cause a denial of service via null pointer dereference in the xlnt library's XLSX parser.","url":"https://insights.sbomify.com/CVE-2026-3665/"}