node-qpdf vulnerable to command injection

published 2023-10-14 3 y ago modified 2026-06-17 4 mo ago also GHSA-fpr8-4wvx-j9q3 , EUVD-2023-2729

cvss: 7.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 2.2%; EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits: 0; none known

All versions of the package node-qpdf are vulnerable to Command Injection such that the package-exported method encrypt() fails to sanitize its parameter input, which later flows into a sensitive command execution API. As a result, attackers may inject malicious commands once they can specify the input pdf file path.

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 2 y ago (2024-09-17)

Exploit prediction

2.19% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

security.snyk.io https://security.snyk.io/vuln/SNYK-JS-NODEQPDF-5747918 referenced PoC, tagged "exploit" by a source, unverified
github.com https://github.com/nrhirani/node-qpdf/issues/23 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P
CNA	3.1	7.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	7.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem	package	affected	fixed in
npm	node-qpdf	<=1.0.3	no fix listed

Affected products

n/a node-qpdf

Classification

Weakness

CWE-78 Improper Neutralization of Special Elements used in an OS Command
CWE-77 Improper Neutralization of Special Elements used in a Command
CWE-94 Improper Control of Generation of Code

References

security.snyk.io /vuln/SNYK-JS-NODEQPDF-5747918
web, exploit, third-party-advisory
github.com /nrhirani/node-qpdf/issues/23
web, exploit, issue-tracking
nvd.nist.gov /vuln/detail/CVE-2023-26155
advisory
github.com /nrhirani/node-qpdf
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary