Quick answers
- Is CVE-2026-26830 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26830 being exploited in the wild.
- How severe is CVE-2026-26830?
- Low severity, with a CVSS score of 3.1, published 25 March 2026.
- Which products and versions are affected?
- pdf-image (npm) SEMVER:introduced=0,last_affected=2.0.0.
- Is there a fix for CVE-2026-26830?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-26830 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-26830?
- Check whether you run pdf-image (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a classic OS command injection (CWE-78) in the constructGetInfoCommand and constructConvertCommandForPage functions, which use util.format() to interpolate unsanitized user-controlled pdfFilePath parameters directly into shell command strings executed via child_process.exec(). An unauthenticated attacker can supply a malicious file path containing shell metacharacters to achieve arbitrary command execution with the privileges of the Node.js process. The vulnerability affects all versions up to and including 2.0.0. No patch is currently available; users should avoid passing unsanitized user input to the pdfFilePath parameter or transition away from this archived library.
Affected products
- mooz pdf-image through 2.0.0
Identifiers
- CVE-2026-26830
- GHSA-q5mh-72xg-628w
Timeline
- 2026-03-25: disclosed: Published to GitHub Advisory Database and NVD
- 2020-04-15: other: Repository archived on GitHub, marked read-only