VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

jspdf: vulnerability history, versions and safety

jspdf is a package in the npm ecosystem. Vulert records 18 vulnerabilities for it across 33 releases, from Mar 2021 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded C2 H12 M4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
12 in the last 12 months

Most recent disclosure 17 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jspdf vulnerabilities

Vulert verdict on jspdf 4.2.1 i

Updated on 23 Oct 2026

Good news: 4.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 18.

Package health score 63/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 4.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.2.1 — unaffected i
  • Vulnerabilities on record 18 over 5 years · 12 in the last year i
  • Latest disclosure 17 Mar 2026 i
  • Highest CVSS 9.6 i
  • With no published fix 0 i
  • Depended on by 767 packages i
  • Stars 31,310 i
  • Last release 7 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for jspdf, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.2.1 17 Mar 2026 none MIT — Details →
4.2.0 19 Feb 2026 C1 H1 MIT Yes Details →
4.1.0 02 Feb 2026 C1 H6 MIT Yes Details →
4.0.0 03 Jan 2026 C1 H8 M2 MIT Yes Details →
3.0.4 19 Nov 2025 C2 H8 M2 MIT Yes Details →
3.0.3 18 Sep 2025 C2 H8 M2 MIT Yes Details →
3.0.2 26 Aug 2025 C2 H8 M2 MIT Yes Details →
3.0.1 18 Mar 2025 C2 H10 M2 MIT Yes Details →
3.0.0 19 Feb 2025 C2 H11 M2 MIT Yes Details →
2.5.2 17 Sep 2024 C2 H11 M2 MIT Yes Details →
2.5.1 28 Jan 2022 C2 H11 M2 MIT Yes Details →
2.5.0 21 Dec 2021 C2 H11 M2 MIT Yes Details →
2.4.0 14 Sep 2021 C2 H11 M2 MIT Yes Details →
2.3.1 09 Mar 2021 C2 H11 M2 MIT Yes Details →
2.3.0 15 Jan 2021 C2 H12 M2 MIT Yes Details →
2.2.0 07 Dec 2020 C2 H12 M2 MIT Yes Details →
2.1.1 07 Sep 2020 C2 H12 M2 MIT Yes Details →
2.1.0 25 Aug 2020 C2 H12 M2 MIT Yes Details →
2.0.0 11 Aug 2020 C2 H12 M2 MIT Yes Details →
1.5.3 27 Dec 2018 C2 H12 M4 MIT Yes Details →
1.5.2 20 Dec 2018 C2 H12 M4 MIT Yes Details →
1.5.1 20 Dec 2018 C2 H12 M4 MIT Yes Details →
1.4.1 06 Jun 2018 C2 H12 M4 MIT Yes Details →
1.4.0 21 May 2018 C2 H12 M4 MIT Yes Details →
1.3.5 14 Sep 2017 C2 H12 M4 MIT Yes Details →
1.3.4 14 Sep 2017 C2 H12 M4 MIT Yes Details →
1.3.3 23 Feb 2017 C2 H12 M4 MIT Yes Details →
1.3.2 30 Sep 2016 C2 H12 M4 MIT Yes Details →
1.3.1 30 Sep 2016 C2 H12 M4 MIT Yes Details →
1.3.0 28 Sep 2016 C2 H12 M4 MIT Yes Details →
1.2.61 01 Mar 2016 C2 H12 M4 MIT Yes Details →
1.2.60 29 Feb 2016 C2 H12 M4 MIT Yes Details →
1.1.135 29 Feb 2016 C2 H12 M4 MIT Yes Details →
1.0.272 19 May 2015 C2 H12 M4 MIT Yes Details →

All 34 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 3
  • 2025 3
  • 2026 12

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 12 of the 18 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jspdf

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-31938: jsPDF HTML Injection Vulnerability in New Window Paths 9.6 critical 4.2.1 17 Mar 2026
Critical Local File Inclusion Vulnerability in jsPDF Package 9.2 critical 4.0.0 05 Jan 2026
CVE-2026-24133: jsPDF Denial of Service Vulnerability via Unvalidated BMP Dimensions 8.7 high 4.1.0 02 Feb 2026
CVE-2026-25535: jsPDF Denial of Service via Malicious GIF Dimensions 8.7 high 4.2.0 19 Feb 2026
jsPDF Denial of Service Vulnerability: Bypass Regular Expression (ReDoS) 8.7 high 3.0.1 18 Mar 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 jspdf

Is jspdf safe to use?

Vulert records 18 vulnerabilities for jspdf in npm: 2 critical, 12 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is jspdf's Vulert package health score?

Vulert scores jspdf 63/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of jspdf affected?

No. 4.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of jspdf should I use?

4.2.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does jspdf have?

18 vulnerabilities are recorded for jspdf in the npm ecosystem: 2 critical, 12 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jspdf vulnerabilities disclosed?

12 vulnerabilities were recorded for jspdf in the last 12 months, and the oldest entry in this database dates to 12 Mar 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jspdf are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor jspdf for upcoming vulnerabilities?

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