CVE-2026-24043: jsPDF Vulnerable to Stored XMP Metadata Injection (Spoofing & Integrity Violation)
Impact 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.
Published Feb 2, 2026 · Updated Feb 3, 2026
Affected packages
jspdf
- Ecosystem
- npm
- Affected
- <= 4.0.0
- Fixed in
- 4.1.0
- Check
npm ls jspdf
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Example attack vector:
import { jsPDF } from "jspdf"
const doc = new jsPDF()
// Input a string that closes the current XML tag and opens a new one.
// We are injecting a fake "dc:creator" (Author) to spoof the document source.
const maliciousInput = '</jspdf:metadata></rdf:Description>' +
'<rdf:Description xmlns:dc="http://purl.org/dc/elements/1.1/">' +
'<dc:creator>TRUSTED_ADMINISTRATOR</dc:creator>' + // <--- Spoofed Identity
'</rdf:Description>' +
'<rdf:Description><jspdf:metadata>'
// The application innocently adds the user's input to the metadata
doc.addMetadata(maliciousInput, "http://valid.namespace")
doc.save("test.pdf")Patches
The vulnerability has been fixed in [email protected]
Workarounds
Sanitize user input before passing it to the addMetadata method: escape XML entities. For example:
let input = "..."
input = input
.replace(/&/g, "&")
.replace(/</g, "<")
.replace(/>/g, ">")
.replace(/"/g, """)
.replace(/'/g, "'")
doc.addMetadata(input)Credited to KarimTantawey.
References
- https://github.com/parallax/jsPDF/security/advisories/GHSA-vm32-vv63-w422
- https://github.com/parallax/jsPDF/commit/efe54bf50f3f5e5416b2495e3c24624fc80b6cff
- https://nvd.nist.gov/vuln/detail/CVE-2026-24043
- https://github.com/parallax/jsPDF/releases/tag/v4.1.0
- https://github.com/advisories/GHSA-vm32-vv63-w422
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-31898
jsPDF has a PDF Object Injection via FreeText color
high8.1Mar 17, 2026CVE-2026-31938
jsPDF has HTML Injection in New Window paths
critical9.6Mar 17, 2026CVE-2026-25535
jsPDF Affected by Client-Side/Server-Side Denial of Service via Malicious GIF Dimensions
high8.7Feb 19, 2026CVE-2026-25755
jsPDF has a PDF Object Injection via Unsanitized Input in addJS Method
high8.1Feb 19, 2026CVE-2026-25940
jsPDF has a PDF Injection in AcroForm module allows Arbitrary JavaScript Execution (RadioButton.createOption and "AS" property)
high8.1Feb 19, 2026CVE-2026-24040
jsPDF has Shared State Race Condition in addJS Plugin
medium6.3Feb 2, 2026
