{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40029 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-40029 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40029 is a high-severity command injection vulnerability in khyrenz parseusbs, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40029 and fix it if it is affected.\n\nWhat it is: CVE-2026-40029 is a high-severity command injection vulnerability in khyrenz parseusbs, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40029 in the wild and no public exploit code.\n\nAffected product: khyrenz parseusbs. 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-40029/ (Markdown: https://insights.sbomify.com/CVE-2026-40029/index.md)","id":"CVE-2026-40029","markdown":"https://insights.sbomify.com/CVE-2026-40029/index.md","name":"CVE-2026-40029","record":{"aliases":["GHSA-2m8h-6748-cf32"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"USB forensic parser","requires_auth":"none","summary":"Attackers can execute arbitrary commands on forensic examiners' machines by crafting malicious LNK filenames processed by the parseusbs tool.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"parseusbs","vendor":"khyrenz"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"parseusbs before 1.9 contains an OS command injection vulnerability in parseUSBs.py where LNK file paths are passed unsanitized into an os.popen() shell command, allowing arbitrary command execution via crafted .lnk filenames containing shell metacharacters. An attacker can craft a .lnk filename with embedded shell metacharacters that execute arbitrary commands on the forensic examiner's machine during USB artifact parsing.","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":"parseusbs \u003c 1.9 Command Injection via Crafted LNK Filename","id":"CVE-2026-40029","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"parseusbs \u003c 1.9 Command Injection via Volume Path Argument","id":"CVE-2026-40030"},"packages":[],"prev":{"headline":"Hayabusa \u003c 3.8.0 XSS via JSON Log Import","id":"CVE-2026-40028"},"products":["parseusbs"],"published":"2026-04-08","related":[{"cvss_score":8.4,"headline":"parseusbs \u003c 1.9 Command Injection via Volume Path Argument","id":"CVE-2026-40030","kev_date_added":null,"published":"2026-04-08"}],"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":"total"},"state":"PUBLISHED","updated":"2026-10-27","vendors":["khyrenz"]},"summary":"Attackers can execute arbitrary commands on forensic examiners' machines by crafting malicious LNK filenames processed by the parseusbs tool.","url":"https://insights.sbomify.com/CVE-2026-40029/"}