{"answers":{"affected":"2 open source packages ship an affected version, including jspdf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24043 in the wild and no public exploit code.","fix":"Upgrade jspdf to 4.1.0 or later.","what":"CVE-2026-24043 is a medium-severity code injection vulnerability in parallax jsPDF, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-24043 and fix it if it is affected.\n\nWhat it is: CVE-2026-24043 is a medium-severity code injection vulnerability in parallax jsPDF, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-24043 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jspdf (npm): affected all versions; fixed in 4.1.0\n- jspdf (npm): affected all versions; fixed in 4.1.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24043/ (Markdown: https://insights.sbomify.com/CVE-2026-24043/index.md)","id":"CVE-2026-24043","markdown":"https://insights.sbomify.com/CVE-2026-24043/index.md","name":"CVE-2026-24043","record":{"aliases":["GHSA-vm32-vv63-w422"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript PDF library","requires_auth":"none","summary":"Attackers can inject arbitrary XML into PDFs via the addMetadata function, compromising document integrity and enabling spoofing in signed or processed files.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jspdf","vendor":"parall"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"jsPDF Affected by Stored XMP Metadata Injection (Spoofing \u0026 Integrity Violation)","id":"CVE-2026-24043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"ESS Community Helm Chart has a weak server key generation method","id":"CVE-2026-24044"},"packages":[{"ecosystem":"npm","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jspdf","purl":null,"source":"GHSA-vm32-vv63-w422"},{"ecosystem":"npm","fixed":["4.1.0"],"introduced":["0"],"last_affected":[],"package":"jspdf","purl":"pkg:npm/jspdf","source":"GHSA-vm32-vv63-w422"}],"prev":{"headline":"Appsmith public apps can execute unpublished actions (viewMode confusion)","id":"CVE-2026-24042"},"products":["jsPDF"],"published":"2026-02-02","related":[{"cvss_score":9.6,"headline":"jsPDF has HTML Injection in New Window paths","id":"CVE-2026-31938","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":9.2,"headline":"jsPDF has Local File Inclusion/Path Traversal vulnerability","id":"CVE-2025-68428","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":8.7,"headline":"jsPDF Affected by Client-Side/Server-Side Denial of Service via Malicious GIF Dimensions","id":"CVE-2026-25535","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":8.7,"headline":"jsPDF Affected by Denial of Service (DoS) via Unvalidated BMP Dimensions in BMPDecoder","id":"CVE-2026-24133","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.7,"headline":"jsPDF Parsing of Corrupt PNGs Leads to Potential Denial of Service (DoS)","id":"CVE-2025-57810","kev_date_added":null,"published":"2025-08-26"},{"cvss_score":8.7,"headline":"jsPDF Bypass Regular Expression Denial of Service (ReDoS)","id":"CVE-2025-29907","kev_date_added":null,"published":"2025-03-18"},{"cvss_score":8.1,"headline":"jsPDF has a PDF Object Injection via FreeText color","id":"CVE-2026-31898","kev_date_added":null,"published":"2026-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-03","vendors":["parallax"]},"summary":"Attackers can inject arbitrary XML into PDFs via the addMetadata function, compromising document integrity and enabling spoofing in signed or processed files.","url":"https://insights.sbomify.com/CVE-2026-24043/"}