# CVE-2026-26830: pdf-image (Critical 9.8)

📦

📦 npm

Not in CISA KEV

CRITICAL severity

# CVE-2026-26830 — pdf-image

CRITICAL 

CVE-2026-26830 is a critical-severity (CVSS 9.8) Code Injection vulnerability in pdf-image. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

pdf-image has an OS Command Injection Vulnerability through its pdfFilePath parameter

Published

Mar 25, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## Exploitation Status

### Proof-of-concept exploit code exists

-   CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
-   CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
-   A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-26830.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs85th percentile — riskier than 85% of all scored CVEsHighest risk

0.00%1.37%2.74%4.12%0.8%2.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

26other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

`pdf-image`npm

11Kdownloads / week

## Description

pdf-image (npm package) through version 2.0.0 allows OS command injection via the pdfFilePath parameter. The constructGetInfoCommand and constructConvertCommandForPage functions use util.format() to interpolate user-controlled file paths into shell command strings that are executed via child\_process.exec().

## Affected Packages

1 total

Ecosystem

Package

Vulnerable range

Fix

📦npm

`pdf-image` 

all versions

No fix

## Affected Products

1 product · 1 configurations

Application

`pdf-image`pdf-image\_project

≤ 2.0.0

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pdf-image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Remediation status
    
    The records we use list no patched version of pdf-image for CVE-2026-26830. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
    
3.  ### Mitigate without a patch
    
    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
    

## Frequently Asked Questions

pdf-image (npm package) through version 2.0.0 allows OS command injection via the pdfFilePath parameter. The constructGetInfoCommand and constructConvertCommandForPage functions use util.format() to interpolate user-controlled file paths into shell command strings that are executed via child\_process.exec().

O3 Security · Impact-Aware SCA

### Is CVE-2026-26830 in your dependencies?

Find it across npm, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)