CVE-2026-24043: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in parallax jsPDF
jsPDF is a library to generate PDFs in JavaScript. Prior to 4.1.0, user control of the first argument of the addMetadata function allows users to inject arbitrary XML. If given the possibility to pass unsanitized input to the addMetadata method, a user can inject arbitrary XMP metadata into the generated PDF. If the generated PDF is signed, stored or otherwise processed after, the integrity of the PDF can no longer be guaranteed. The vulnerability has been fixed in jsPDF@4.1.0.
AI Analysis
Technical Summary
CVE-2026-24043 is an injection vulnerability classified under CWE-74 affecting the parallax jsPDF library, a widely used JavaScript tool for generating PDF documents client-side or server-side. The flaw exists in versions prior to 4.1.0 where the addMetadata function accepts user-controlled input as its first argument without proper sanitization or neutralization of special XML characters. This allows an attacker to inject arbitrary XMP metadata into the generated PDF files. Since XMP metadata can be embedded deeply within PDFs and may be used for digital signatures, document validation, or archival purposes, the injection undermines the integrity guarantees of the PDF. If a PDF is signed or processed by downstream systems relying on metadata integrity, the injected XML can cause trust violations or manipulation of document metadata. The vulnerability is remotely exploitable without authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N) indicates network attack vector, low attack complexity, no privileges or user interaction required, no confidentiality or availability impact, but partial integrity impact with limited scope. The issue was publicly disclosed on February 2, 2026, and fixed in jsPDF version 4.1.0. No known exploits have been reported in the wild to date. Organizations using jsPDF versions below 4.1.0 should prioritize upgrading to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of PDF documents generated using vulnerable jsPDF versions. Industries relying on digitally signed PDFs for contracts, legal documents, financial reports, or regulatory submissions could face document trust issues if malicious metadata injection occurs. This could lead to legal disputes, compliance violations, or reputational damage. Since jsPDF is popular in web applications and internal tools, any automated PDF generation pipeline that does not sanitize metadata inputs is vulnerable. The injection does not directly compromise confidentiality or availability but undermines the reliability of document metadata, which can affect audit trails and digital signature verification. Organizations in sectors such as finance, legal, government, and healthcare in Europe, where document integrity is critical, are particularly at risk. The lack of known exploits reduces immediate threat but does not eliminate the risk of future attacks. The vulnerability’s remote exploitability without authentication increases the attack surface, especially for public-facing applications.
Mitigation Recommendations
European organizations should immediately upgrade all instances of jsPDF to version 4.1.0 or later to ensure the vulnerability is patched. For legacy systems where upgrading is not immediately feasible, implement strict input validation and sanitization on any user-supplied data passed to the addMetadata function to neutralize special XML characters and prevent injection. Employ PDF signing and verification tools that validate the integrity of both the document content and metadata to detect tampering. Incorporate security testing in the development lifecycle to identify unsanitized metadata inputs. Monitor PDF generation workflows for anomalies in metadata fields. Additionally, restrict access to PDF generation endpoints to trusted users and networks to reduce exposure. Educate developers about secure handling of metadata in PDFs and the risks of injection attacks. Finally, maintain an inventory of applications using jsPDF to ensure comprehensive patching and risk assessment.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Belgium, Sweden, Poland, Ireland
CVE-2026-24043: CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') in parallax jsPDF
Description
jsPDF is a library to generate PDFs in JavaScript. Prior to 4.1.0, user control of the first argument of the addMetadata function allows users to inject arbitrary XML. If given the possibility to pass unsanitized input to the addMetadata method, a user can inject arbitrary XMP metadata into the generated PDF. If the generated PDF is signed, stored or otherwise processed after, the integrity of the PDF can no longer be guaranteed. The vulnerability has been fixed in jsPDF@4.1.0.
AI-Powered Analysis
Technical Analysis
CVE-2026-24043 is an injection vulnerability classified under CWE-74 affecting the parallax jsPDF library, a widely used JavaScript tool for generating PDF documents client-side or server-side. The flaw exists in versions prior to 4.1.0 where the addMetadata function accepts user-controlled input as its first argument without proper sanitization or neutralization of special XML characters. This allows an attacker to inject arbitrary XMP metadata into the generated PDF files. Since XMP metadata can be embedded deeply within PDFs and may be used for digital signatures, document validation, or archival purposes, the injection undermines the integrity guarantees of the PDF. If a PDF is signed or processed by downstream systems relying on metadata integrity, the injected XML can cause trust violations or manipulation of document metadata. The vulnerability is remotely exploitable without authentication or user interaction, increasing its risk profile. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N) indicates network attack vector, low attack complexity, no privileges or user interaction required, no confidentiality or availability impact, but partial integrity impact with limited scope. The issue was publicly disclosed on February 2, 2026, and fixed in jsPDF version 4.1.0. No known exploits have been reported in the wild to date. Organizations using jsPDF versions below 4.1.0 should prioritize upgrading to mitigate this risk.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to the integrity of PDF documents generated using vulnerable jsPDF versions. Industries relying on digitally signed PDFs for contracts, legal documents, financial reports, or regulatory submissions could face document trust issues if malicious metadata injection occurs. This could lead to legal disputes, compliance violations, or reputational damage. Since jsPDF is popular in web applications and internal tools, any automated PDF generation pipeline that does not sanitize metadata inputs is vulnerable. The injection does not directly compromise confidentiality or availability but undermines the reliability of document metadata, which can affect audit trails and digital signature verification. Organizations in sectors such as finance, legal, government, and healthcare in Europe, where document integrity is critical, are particularly at risk. The lack of known exploits reduces immediate threat but does not eliminate the risk of future attacks. The vulnerability’s remote exploitability without authentication increases the attack surface, especially for public-facing applications.
Mitigation Recommendations
European organizations should immediately upgrade all instances of jsPDF to version 4.1.0 or later to ensure the vulnerability is patched. For legacy systems where upgrading is not immediately feasible, implement strict input validation and sanitization on any user-supplied data passed to the addMetadata function to neutralize special XML characters and prevent injection. Employ PDF signing and verification tools that validate the integrity of both the document content and metadata to detect tampering. Incorporate security testing in the development lifecycle to identify unsanitized metadata inputs. Monitor PDF generation workflows for anomalies in metadata fields. Additionally, restrict access to PDF generation endpoints to trusted users and networks to reduce exposure. Educate developers about secure handling of metadata in PDFs and the risks of injection attacks. Finally, maintain an inventory of applications using jsPDF to ensure comprehensive patching and risk assessment.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-01-20T22:30:11.777Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69813005f9fa50a62f63a3d6
Added to database: 2/2/2026, 11:15:17 PM
Last enriched: 2/2/2026, 11:31:59 PM
Last updated: 2/5/2026, 7:24:28 PM
Views: 13
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-25630
UnknownCVE-2026-1301: CWE-787 Out-of-bounds Write in o6 Automation GmbH Open62541
MediumCVE-2026-1707: Vulnerability in pgadmin.org pgAdmin 4
HighCVE-2025-68121: CWE-295: Improper Certificate Validation in Go standard library crypto/tls
HighCVE-2025-58190: CWE-835: Loop with Unreachable Exit Condition in golang.org/x/net golang.org/x/net/html
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.