{"answers":{"affected":"2 open source packages ship an affected version, including dompurify.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41238 exists.","fix":"Upgrade dompurify to 3.4.0 or later.","what":"CVE-2026-41238 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-41238 and fix it if it is affected.\n\nWhat it is: CVE-2026-41238 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41238 exists.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected from 3.0.1; fixed in 3.4.0\n- dompurify (npm): affected from 3.0.1; 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-41238/ (Markdown: https://insights.sbomify.com/CVE-2026-41238/index.md)","id":"CVE-2026-41238","markdown":"https://insights.sbomify.com/CVE-2026-41238/index.md","name":"CVE-2026-41238","record":{"aliases":["CLEANSTART-2026-AM93725","CLEANSTART-2026-NT67628","DEBIAN-CVE-2026-41238","ECHO-951f-211f-5fc7","GHSA-v9jr-rg53-9pgp","MINI-3gqp-x9f3-2wrx","MINI-483m-mfpp-6fq7","MINI-4j9r-hx2w-h7gc","MINI-6mjp-mpx7-3h6g","MINI-85m4-crvh-qj43","MINI-9qwr-h932-vr9r","MINI-9x7m-846f-xw93","MINI-c495-gp43-cgqw","MINI-hh8p-854j-whf5","MINI-jp47-f58r-r2mr","MINI-w5cm-gf9p-74gp","ROOT-APP-NPM-CVE-2026-41238","UBUNTU-CVE-2026-41238"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript HTML sanitizer","requires_auth":"none","summary":"Prototype pollution allows bypassing DOMPurify sanitization, enabling XSS attacks via injected custom elements and attributes.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"DOMPurify is a DOM-only cross-site scripting sanitizer for HTML, MathML, and SVG. Versions 3.0.1 through 3.3.3 are vulnerable to a prototype pollution-based XSS bypass. When an application uses `DOMPurify.sanitize()` with the default configuration (no `CUSTOM_ELEMENT_HANDLING` option), a prior prototype pollution gadget can inject permissive `tagNameCheck` and `attributeNameCheck` regex values into `Object.prototype`, causing DOMPurify to allow arbitrary custom elements with arbitrary attributes — including event handlers — through sanitization. Version 3.4.0 fixes the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"DOMPurify: Prototype Pollution to XSS Bypass via CUSTOM_ELEMENT_HANDLING Fallback","id":"CVE-2026-41238","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 has a SAFE_FOR_TEMPLATES bypass in RETURN_DOM mode","id":"CVE-2026-41239"},"packages":[{"ecosystem":"npm","fixed":["3.4.0"],"introduced":["3.0.1"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-v9jr-rg53-9pgp"},{"ecosystem":"npm","fixed":["3.4.0"],"introduced":["3.0.1"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-v9jr-rg53-9pgp"}],"prev":{"headline":"Froxlor has an incomplete fix for CVE-2026-30932","id":"CVE-2026-41237"},"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["cure53"]},"summary":"Prototype pollution allows bypassing DOMPurify sanitization, enabling XSS attacks via injected custom elements and attributes.","url":"https://insights.sbomify.com/CVE-2026-41238/"}