{"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-65902 exists.","fix":"Upgrade dompurify to 3.4.7 or later.","what":"CVE-2026-65902 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 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-65902 and fix it if it is affected.\n\nWhat it is: CVE-2026-65902 is a medium-severity cross-site scripting vulnerability in cure53 DOMPurify, published on 23 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-65902 exists.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected all versions; fixed in 3.4.7\n- dompurify (npm): affected all versions; fixed in 3.4.7\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-65902/ (Markdown: https://insights.sbomify.com/CVE-2026-65902/index.md)","id":"CVE-2026-65902","markdown":"https://insights.sbomify.com/CVE-2026-65902/index.md","name":"CVE-2026-65902","record":{"aliases":["DEBIAN-CVE-2026-65902","ECHO-cf5d-0476-1b92","GHSA-76mc-f452-cxcm","MINI-3jw8-r6qm-fvhj","MINI-4h9c-jvjc-pr38","MINI-5j9c-vhf8-pm8h","MINI-65pv-vqgh-3cq5","MINI-65pw-9mhq-7fm7","MINI-8w85-5gcm-vcq5","MINI-8xpw-4prm-2cw2","MINI-cxcc-w83r-7g3x","MINI-gr8w-j2rc-h4pm","MINI-h28r-cqgq-5xf2","MINI-hv43-69w9-3579","MINI-rcrh-5gq9-j6mq","MINI-v826-3fgf-wwf8","MINI-vcjh-328f-pfxq","MINI-w4c5-6c9w-25wp","MINI-xh5q-97wq-8jv9","MINI-xp2g-q6hv-4g8c","ROOT-APP-NPM-CVE-2026-65902","ROOT-APP-NPM-GHSA-76mc-f452-cxcm","UBUNTU-CVE-2026-65902"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sanitization library","requires_auth":"none","summary":"DOMPurify allows persistent allow-list pollution via hooks, enabling XSS by bypassing sanitization for subsequent calls.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"dompurify","vendor":"cure53"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-501","name":"Trust Boundary Violation"}],"description":"DOMPurify before 3.4.7 passes direct references to the module-level DEFAULT_ALLOWED_TAGS and DEFAULT_ALLOWED_ATTR sets to the uponSanitizeElement and uponSanitizeAttribute hooks via data.allowedTags / data.allowedAttributes when sanitize is called without an explicit cfg.ALLOWED_TAGS / cfg.ALLOWED_ATTR array. A hook that mutates these fields permanently widens the default allow-lists for the lifetime of the DOMPurify instance, so all subsequent default-config sanitize calls inherit the widened defaults and attacker payloads using the poisoned tag/attribute name survive sanitization. removeAllHooks(), clearConfig(), and passing a fresh cfg do not recover the state; only constructing a new DOMPurify instance does.","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.7 Hook Mutation Pollution via allowedTags","id":"CVE-2026-65902","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"DOMPurify before 3.4.0 ADD_TAGS Function Bypasses FORBID_TAGS","id":"CVE-2026-65903"},"packages":[{"ecosystem":"npm","fixed":["3.4.7"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-76mc-f452-cxcm"},{"ecosystem":"npm","fixed":["3.4.7"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-76mc-f452-cxcm"}],"prev":{"headline":"DOMPurify 3.4.6 Cross-Site Scripting via IN_PLACE nodeName","id":"CVE-2026-65901"},"products":["DOMPurify"],"published":"2026-07-23","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-10-29","vendors":["cure53"]},"summary":"DOMPurify allows persistent allow-list pollution via hooks, enabling XSS by bypassing sanitization for subsequent calls.","url":"https://insights.sbomify.com/CVE-2026-65902/"}