jspdf (npm) has 15 known vulnerabilities, the worst rated CRITICAL. Upgrade to 4.2.1 or later to clear all of them. No malicious-package signal is recorded.
User control of the options argument of the output function allows attackers to inject arbitrary HTML (such as scripts) into the browser context the created…
CyberXYZ does not call a package safe in absolute terms. It records 15 known vulnerabilities for jspdf (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does jspdf have known vulnerabilities?
Yes. CyberXYZ records 15 known vulnerabilities for jspdf (npm), the worst rated CRITICAL. These include GHSA-wfv2-pwc8-crg5, GHSA-f8cm-6447-x5h2, GHSA-7x6v-j9x4-qf24, GHSA-p5xg-68wr-hm3m, GHSA-67pg-wm7f-q7fj.
Which version of jspdf should I use?
4.2.1 or later clears every advisory recorded for jspdf (npm). Check the release you pick before installing it.
How do I check jspdf before installing?
Search jspdf in CyberXYZ Check at https://cyberxyz.io/check?q=jspdf. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:23 UTC. The most recent advisory here was published 2026-03-17. Updated continuously from NVD, GHSA, OSV and CNA feeds.