VulnerabilityPublished 2 Feb 2026

CVE-2026-24043: parallax jsPDF · Injection

Affects parallax jsPDFSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.1.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: Low
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade jsPDF and jspdf to 4.1.0.

Affected software

Product	Affected	Fixed in
parallaxjsPDF	Affected <4.1.0	Fixed in 4.1.0
npmjspdf`pkg:npm/jspdf`Other threats	Affected <4.1.0	Fixed in 4.1.0

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 instances of jsPDF to version 4.1.0 or later, where the vulnerability has been fixed. Organizations should audit their codebases and dependencies to identify usage of vulnerable jsPDF versions, especially in web applications or services that generate PDFs. Additionally, implement strict input validation and sanitization on any data passed to the addMetadata function to prevent injection of malicious XML content. Employ security code reviews and automated scanning tools to detect unsafe usage patterns. For critical environments, consider implementing PDF integrity verification processes post-generation to detect anomalies in metadata. Educate developers about secure handling of third-party libraries and the risks of unsanitized input in document generation contexts. Finally, monitor security advisories for any emerging exploits related to this vulnerability and apply patches promptly.

Description

CVE-2026-24043 is a medium severity vulnerability in the jsPDF JavaScript library versions prior to 4.1.0. It allows an attacker to inject arbitrary XML into the XMP metadata of generated PDFs via unsanitized input to the addMetadata function. This injection can compromise the integrity of PDFs, especially if they are signed or processed later. The vulnerability requires no authentication or user interaction and can be exploited remotely. The issue has been fixed in jsPDF version 4.1.0. European organizations using vulnerable jsPDF versions in their web applications or services that generate PDFs should update promptly to prevent potential integrity issues.

Impact

For European organizations, this vulnerability poses a risk to the integrity of PDF documents generated using vulnerable jsPDF versions. This is particularly critical for sectors that rely on digitally signed PDFs for legal, financial, or regulatory compliance purposes, such as banking, government, healthcare, and legal services. An attacker injecting malicious XML metadata could cause signature validation failures or introduce misleading metadata, potentially leading to document repudiation or manipulation. This undermines trust in document authenticity and could disrupt workflows dependent on automated PDF processing or archiving. Since jsPDF is widely used in web applications and client-side PDF generation, organizations embedding this library without proper updates may inadvertently expose themselves to integrity attacks. Although no confidentiality or availability impact is directly indicated, the loss of integrity in signed documents can have severe operational and reputational consequences.

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Implementation
Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Server Side Include (SSI) Injection (opens in a new tab)
HTTP Request Splitting (opens in a new tab)
Command Line Execution through SQL Injection (opens in a new tab)
Double Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Feb 2026, 11:10 UTC

WeaknessesCWE-74

Technical details

References

Community reviews

Related threats