Quick answers
- Is CVE-2025-57810 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-57810 being exploited in the wild.
- How severe is CVE-2025-57810?
- Low severity, with a CVSS score of 3.1, published 26 August 2025.
- Which products and versions are affected?
- jspdf (npm) SEMVER:introduced=0,fixed=3.0.2.
- Is there a fix for CVE-2025-57810?
- Yes. jspdf (npm): upgrade to 3.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-57810 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-57810?
- Check whether you run jspdf (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- jspdf (npm): upgrade to 3.0.2 or later
npm install jspdf@3.0.2
Technical details
The vulnerability is a denial-of-service flaw in the addImage() method and related HTML rendering functions, triggered by improper validation of PNG image data (CWE-20, CWE-835). When an attacker provides a malformed PNG file or URL to addImage(), the library enters an infinite or very long-running loop while attempting to parse the image, causing CPU exhaustion. The attack requires only network access with no authentication or user interaction; any application using jsPDF that accepts unsanitized image input is vulnerable. The flaw was patched in jsPDF 3.0.2, which now throws an error for invalid PNG files instead of hanging.
Affected products
- parallax jsPDF <= 3.0.1
Identifiers
- CVE-2025-57810
- GHSA-8mvj-3j78-4qmw
Timeline
- 2025-08-26: disclosed
- 2025-08-26: patched: jsPDF 3.0.2 released