{"answers":{"affected":"2 open source packages ship an affected version, including dompurify.","exploited":"There is no known exploitation of CVE-2026-41239 in the wild and no public exploit code.","fix":"Upgrade dompurify to 3.4.0 or later.","what":"CVE-2026-41239 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-41239 and fix it if it is affected.\n\nWhat it is: CVE-2026-41239 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-41239 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected from 1.0.10; fixed in 3.4.0\n- dompurify (npm): affected from 1.0.10; fixed in 3.4.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-41239/ (Markdown: https://insights.sbomify.com/CVE-2026-41239/index.md)","id":"CVE-2026-41239","markdown":"https://insights.sbomify.com/CVE-2026-41239/index.md","name":"CVE-2026-41239","record":{"aliases":["CLEANSTART-2026-EP14815","CLEANSTART-2026-JJ46339","DEBIAN-CVE-2026-41239","ECHO-89aa-7e3b-59e1","GHSA-crv5-9vww-q3g8","MINI-2vfm-vhq6-pvrj","MINI-4w56-p8mx-wqr2","MINI-98qr-xm78-73p6","MINI-cgcm-xjj3-v87g","MINI-m3ph-gmxv-4789","MINI-mm6j-g3jr-r525","MINI-pvrg-p79v-r89v","MINI-q553-62cr-7736","MINI-x3xq-ggg9-7xq4","MINI-x48q-28xv-x2cg","MINI-xgvr-qf7x-gjq8","ROOT-APP-NPM-CVE-2026-41239","UBUNTU-CVE-2026-41239"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript HTML sanitizer","requires_auth":"none","summary":"DOMPurify fails to strip template expressions in RETURN_DOM mode, allowing XSS attacks in applications using template-evaluating frameworks like Vue 2.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-1289","name":"Improper Validation of Unsafe Equivalence in Input"}],"description":"DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Starting in version 1.0.10 and prior to version 3.4.0, `SAFE_FOR_TEMPLATES` strips `{{...}}` expressions from untrusted HTML. This works in string mode but not with `RETURN_DOM` or `RETURN_DOM_FRAGMENT`, allowing XSS via template-evaluating frameworks like Vue 2. Version 3.4.0 patches the issue.","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":"DOMPurify has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode","id":"CVE-2026-41239","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"DOMPurify: FORBID_TAGS bypassed by function-based ADD_TAGS predicate (asymmetry with FORBID_ATTR fix)","id":"CVE-2026-41240"},"packages":[{"ecosystem":"npm","fixed":["3.4.0"],"introduced":["1.0.10"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-crv5-9vww-q3g8"},{"ecosystem":"npm","fixed":["3.4.0"],"introduced":["1.0.10"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-crv5-9vww-q3g8"}],"prev":{"headline":"DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback","id":"CVE-2026-41238"},"products":["DOMPurify"],"published":"2026-04-23","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-25","vendors":["cure53"]},"summary":"DOMPurify fails to strip template expressions in RETURN_DOM mode, allowing XSS attacks in applications using template-evaluating frameworks like Vue 2.","url":"https://insights.sbomify.com/CVE-2026-41239/"}