CVE-2025-57810: parallax jsPDF · Improper Input Validation
Affects parallax jsPDFSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 3.0.2 soon.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade parallax jsPDF to 3.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parallax jsPDF | Affected
| Fixed in
|
AI-suggested
To mitigate this vulnerability, European organizations should immediately upgrade all instances of jsPDF to version 3.0.2 or later, where the input validation flaw has been fixed. Beyond patching, developers should implement strict input validation and sanitization on any user-supplied data passed to the addImage method, including verifying image formats and sizes before processing. Employing Web Application Firewalls (WAFs) with rules to detect and block anomalous or malformed image payloads can provide an additional layer of defense. Monitoring CPU utilization and application performance metrics can help detect early signs of exploitation attempts. It is also advisable to conduct code audits and dependency scans regularly to identify and remediate vulnerable library versions. For critical systems, consider isolating PDF generation processes or running them with limited resource quotas to minimize the impact of potential DoS attacks.
Description
jsPDF is a library to generate PDFs in JavaScript. Prior to 3.0.2, 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. The vulnerability was fixed in jsPDF 3.0.2.
References
- github.com/parallax/jsPDF/security/advisories/GHSA-8mvj-3j78-4qmw (opens in a new tab)
- github.com/parallax/jsPDF/pull/3880 (opens in a new tab)
- github.com/parallax/jsPDF/commit/4cf3ab619e565d9b88b4b130bff901b91d8688e9 (opens in a new tab)
- github.com/parallax/jsPDF/releases/tag/v3.0.2 (opens in a new tab)