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

> Attackers can execute arbitrary commands on forensic examiners' machines by crafting malicious LNK filenames processed by the parseusbs tool.

- **Severity:** High 8.5 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Apr 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-2m8h-6748-cf32

## What is CVE-2026-40029?

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.

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

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-40029?

It affects 1 product.


Products: Khyrenz Parseusbs.

## How do I fix CVE-2026-40029?

No fix has been published for CVE-2026-40029 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-40029 being exploited?

There is no known exploitation of CVE-2026-40029 in the wild and no public exploit code.

## Other vulnerabilities in khyrenz parseusbs

- [CVE-2026-40030](https://insights.sbomify.com/CVE-2026-40030/): parseusbs < 1.9 Command Injection via Volume Path Argument (high 8.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40029 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-40029 in the wild and no public exploit code.

Affected product: khyrenz parseusbs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-40029/ (Markdown: https://insights.sbomify.com/CVE-2026-40029/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40029
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40029
- OSV: https://osv.dev/vulnerability/CVE-2026-40029

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-40029/
Summaries are generated and may contain mistakes; the official description above is the record.