CVE-2026-40029

7.8

khyrenz · parseusbs

A command injection vulnerability in parseusbs allows arbitrary code execution on the forensic examiner's machine via maliciously crafted LNK filenames.

Executive summary

A critical OS command injection vulnerability exists in the parseusbs tool, potentially allowing an attacker to execute arbitrary code on a forensic examiner's workstation.

Vulnerability

This is an OS command injection vulnerability (CWE-78) occurring in the parseUSBs.py script, where LNK file paths are passed into an os.popen() call without sanitization. An unauthenticated attacker can exploit this by providing a crafted LNK filename containing shell metacharacters that trigger command execution when the forensic tool parses the file.

Business impact

The successful exploitation of this vulnerability results in full system compromise for the affected forensic examiner, as the malicious commands execute with the privileges of the user running the script. Given the CVSS score of 7.8, this represents a high-severity risk that could lead to data exfiltration, lateral movement within a forensic network, or the compromise of sensitive digital evidence.

Remediation

Immediate Action: Upgrade the parseusbs software to version 1.9.0 or later, which includes the fix for sanitizing LNK file paths.

Proactive Monitoring: Monitor forensic workstations for unexpected child processes spawned by python scripts or unusual shell activity during the ingestion of USB artifacts.

Compensating Controls: Ensure that forensic tools are executed in isolated, non-persistent virtual environments or sandboxes to limit the impact of potential code execution.

Exploitation status

Public Exploit Available: No confirmed public exploit exists in the provided data.

Analyst recommendation

Given the high impact of arbitrary command execution, users of the parseusbs tool should prioritize updating to version 1.9.0 immediately. Forensic teams should also review their ingestion workflows to ensure that untrusted media is handled in secure, restricted environments until the patch is fully deployed.

Sources

Originally found and disclosed by Mobasi Security Team, per the CVE Program record.