{"answers":{"affected":"2 open source packages ship an affected version, including dompurify. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-66010 exists.","fix":"Upgrade dompurify to 3.4.12 or later.","what":"CVE-2026-66010 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 24 Jul 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-66010 and fix it if it is affected.\n\nWhat it is: CVE-2026-66010 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 24 Jul 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-66010 exists.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected all versions; fixed in 3.4.12\n- dompurify (npm): affected all versions; fixed in 3.4.12\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-66010/ (Markdown: https://insights.sbomify.com/CVE-2026-66010/index.md)","id":"CVE-2026-66010","markdown":"https://insights.sbomify.com/CVE-2026-66010/index.md","name":"CVE-2026-66010","record":{"aliases":["CLEANSTART-2026-DT43318","CLSA-2026-1784769541","CLSA-2026-1784769611","CLSA-2026-1784943203","CLSA-2026-1784943304","CLSA-2026-1791798931","CLSA-2026-1791806751","CLSA-2026-1791815045","CLSA-2026-1791821569","CLSA-2026-1791825656","CLSA-2026-1791849797","CLSA-2026-1792163693","DEBIAN-CVE-2026-66010","ECHO-6d8a-f8d5-1592","GHSA-c2j3-45gr-mqc4","MINI-2q3p-jm9x-mr5x","MINI-4f52-vhqf-5r52","MINI-5xmq-cq7r-7mj3","MINI-64f7-pjrw-vq3g","MINI-6jf5-ww9m-7ghr","MINI-f5x3-jgp4-mq94","MINI-gj9x-cxcc-g47g","MINI-jcrc-jmg9-jfrq","MINI-jh25-2g4m-jh7r","MINI-mr5w-7x86-q5qm","MINI-p659-p632-r99v","MINI-pgg4-qcxc-6cww","MINI-v954-762f-f84c","MINI-w4w6-3pv4-g73g","MINI-w96x-c222-32jh","MINI-wr29-r6p4-45g7","MINI-xgvg-59c9-9vjh","MINI-xwff-gxxv-wc9m","UBUNTU-CVE-2026-66010"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript sanitization library","requires_auth":"none","summary":"Attackers can bypass DOMPurify hooks to preserve malicious attributes on custom elements, enabling second-order XSS in applications using this library.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"dompurify","vendor":"cure53"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"DOMPurify before 3.4.12 fails to execute afterSanitizeElements hook for custom elements allowed via CUSTOM_ELEMENT_HANDLING.tagNameCheck, allowing attributes to bypass application security policies. Attackers can preserve sensitive attributes on custom elements that later re-inject them into innerHTML sinks, creating second-order XSS gadgets.","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 before 3.4.12 Hook Bypass via CUSTOM_ELEMENT_HANDLING","id":"CVE-2026-66010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"ImageMagick before 7.1.2-27 Memory Leak via Invalid CLI Options","id":"CVE-2026-66011"},"packages":[{"ecosystem":"npm","fixed":["3.4.12"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-c2j3-45gr-mqc4"},{"ecosystem":"npm","fixed":["3.4.12"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-c2j3-45gr-mqc4"}],"prev":{"headline":"Parse Server 9.0.0 Information Disclosure via GraphQL Error Messages","id":"CVE-2026-66009"},"products":["DOMPurify"],"published":"2026-07-24","related":[{"cvss_score":10,"headline":"DOMPurify nesting-based mXSS","id":"CVE-2024-47875","kev_date_added":null,"published":"2024-10-11"},{"cvss_score":9.1,"headline":"DOMPurify vulnerable to tampering by prototype polution","id":"CVE-2024-48910","kev_date_added":null,"published":"2024-10-31"},{"cvss_score":8.2,"headline":"DOMPurify XSS via `selectedcontent` re-clone","id":"CVE-2026-47423","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":7.3,"headline":"Tampering by prototype polution in DOMPurify","id":"CVE-2024-45801","kev_date_added":null,"published":"2024-09-16"},{"cvss_score":6.3,"headline":"DOMPurify IN_PLACE Sanitization Bypass via Attached Shadow Root Inside \u003ctemplate\u003e.content","id":"CVE-2026-49978","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":6.1,"headline":"DOMPurify: Cross-realm IN_PLACE sanitization leaves executable markup intact via realm-bound `instanceof` checks","id":"CVE-2026-49458","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":6.1,"headline":"DOMPurify: IN_PLACE mode preserves attributes of a clobbered root element, allowing XSS via attacker-controlled root DOM","id":"CVE-2026-49459","kev_date_added":null,"published":"2026-07-14"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["cure53"]},"summary":"Attackers can bypass DOMPurify hooks to preserve malicious attributes on custom elements, enabling second-order XSS in applications using this library.","url":"https://insights.sbomify.com/CVE-2026-66010/"}