CVE-2026-40030: parseusbs before 1.9 contains an OS command injection vulnerability where the volume listing path argument (-v

Q: How do I fix CVE-2026-40030?

parseusbs: upgrade to 1.9. Exact commands for each OS are on this page.

Q: Is CVE-2026-40030 being exploited?

CVE-2026-40030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-40030 affect?

CVE-2026-40030 affects parseusbs. Severity is high (CVSS 7.8). parseusbs before 1.9 contains an OS command injection vulnerability where the volume listing path argument (-v flag) is passed unsanitized into an os.popen() shell command with ls, allowing arbitrary command injection via crafted volume pat

This month

HIGH 7.8UPGRADE

CVE-2026-40030 is a high-severity flaw (CVSS 7.8) affecting parseusbs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

parseusbs before 1.9 contains an OS command injection vulnerability where the volume listing path argument (-v flag) is passed unsanitized into an os.popen() shell command with ls, allowing arbitrary command injection via crafted volume path arguments containing shell metacharacters. An attacker can provide a crafted volume path via the -v flag that injects arbitrary commands during volume content enumeration.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.8% (top 45%)
CISA exploited list	No
Weakness	CWE-78
Published	2026-04-08
Last modified	2026-07-24

Publisher (CNA): VulnCheck · Vendor: khyrenz

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-08 22:16 UTCPublished CVE record published
2026-07-24 21:10 UTCUpdated Record last modified

khyrenz parseusbs UPGRADE

Affected: < 1.9

Fixed in: 1.9

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy parseusbs || rpm -q parseusbs || parseusbs --version

2. UPGRADE to 1.9 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade parseusbs

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade parseusbs

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-40030?

parseusbs: upgrade to 1.9. Exact commands for each OS are on this page.

Is CVE-2026-40030 being exploited?

CVE-2026-40030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-40030 affect?

CVE-2026-40030 affects parseusbs. Severity is high (CVSS 7.8). parseusbs before 1.9 contains an OS command injection vulnerability where the volume listing path argument (-v flag) is passed unsanitized into an os.popen() shell command with ls, allowing arbitrary command injection via crafted volume pat

How urgent is CVE-2026-40030?

Priority 41/100. High severity

Related CVEs

CVE-2026-40029 HIGH 7.8 UPGRADE parseusbs before 1.9 contains an OS command injection vulnerability in parseUSBs.py where LNK file paths are p

References

← Back to latest CVEs