CVE-2026-24040: parallax jsPDF · Race Condition
Affects parallax jsPDFSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.1.0 when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.1.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Feb 2026
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 2026-10-26.
What to do
Upgrade jsPDF and jspdf to 4.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parallaxjsPDF | Affected
| Fixed in
|
npmjspdfpkg:npm/jspdfOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade all jsPDF instances to version 4.1.0 or later, where the race condition has been fixed by removing shared mutable state and implementing proper synchronization. Organizations should audit their Node.js applications to identify usage of vulnerable jsPDF versions, particularly in multi-tenant or concurrent request scenarios. Implementing request-level isolation for PDF generation processes can further reduce risk by preventing shared state across requests. Where upgrading is not immediately feasible, consider serializing PDF generation requests or using separate process instances to avoid concurrent access to shared variables. Conduct thorough testing to ensure no residual race conditions exist in custom PDF generation code. Additionally, review embedded JavaScript usage in PDFs to minimize sensitive data exposure and consider disabling JavaScript in PDFs if not required. Monitoring and logging PDF generation activities can help detect anomalous behavior indicative of exploitation attempts. Finally, ensure compliance with data protection laws by promptly addressing this vulnerability to prevent unauthorized data disclosure.
Description
CVE-2026-24040 is a medium severity race condition vulnerability in the jsPDF library versions prior to 4.1.0. The issue arises from improper synchronization of a shared variable used to store JavaScript content during PDF generation in concurrent Node.js environments. This flaw can cause cross-user data leakage, where PDF documents generated for one user may inadvertently include JavaScript payloads intended for another user, exposing sensitive information. The vulnerability primarily affects server-side usage of jsPDF but could also manifest in client-side scenarios under concurrent execution. Exploitation requires no authentication or user interaction but depends on concurrent PDF generation requests. The vulnerability has been fixed in jsPDF version 4.1.