Vulnerability Database · npm · pdf-image · Version

pdf-image 1.0.1

1.0.1 is affected by 3 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 2 High 1 Medium 0 Low 0 Unrated 0

Released 26 Aug 2015 Licence MIT Also known from other sources 3 Newer releases 8 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

pdf-image 1.0.1 vulnerabilities

3 vulnerabilities cover pdf-image 1.0.1. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2026-26830: pdf-image OS Command Injection Vulnerability via pdfFilePath Parameter 9.8 critical No fix published 25 Mar 2026
CVE-2020-8132: Improper Input Validation and Code Injection in pdf-image 9.8 high No fix published 10 May 2021
CVE-2018-3757: Command Injection in pdf-image 9.8 critical 2.0.0 01 Sep 2020

Looking for another version, or everything Vulert holds for pdf-image?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pdf-image 1.0.1

Is pdf-image 1.0.1 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover pdf-image 1.0.1: 2 critical, 1 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 1.0.1 the latest release of pdf-image?

No. 1.0.1 was published 26 Aug 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor pdf-image for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pdf-image version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.