{"answers":{"affected":"2 open source packages ship an affected version, including dompurify. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-65899 in the wild and no public exploit code.","fix":"Upgrade dompurify to 3.4.9 or later.","what":"CVE-2026-65899 is a medium-severity 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-65899 and fix it if it is affected.\n\nWhat it is: CVE-2026-65899 is a medium-severity 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: There is no known exploitation of CVE-2026-65899 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dompurify (npm): affected all versions; fixed in 3.4.9\n- dompurify (npm): affected all versions; fixed in 3.4.9\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-65899/ (Markdown: https://insights.sbomify.com/CVE-2026-65899/index.md)","id":"CVE-2026-65899","markdown":"https://insights.sbomify.com/CVE-2026-65899/index.md","name":"CVE-2026-65899","record":{"aliases":["DEBIAN-CVE-2026-65899","ECHO-c3fd-1cde-4135","GHSA-vxr8-fq34-vvx9","MINI-2339-gvqj-pgx8","MINI-35vj-mh4c-5f7h","MINI-3f2j-vm92-r68v","MINI-467m-4p6j-5c2q","MINI-499f-xw5m-wv5p","MINI-4cpx-mrcm-9g3h","MINI-4x2j-6w2p-rv54","MINI-524g-p9j3-426x","MINI-5g3h-55cj-47x9","MINI-5p8m-8752-34xf","MINI-6h92-5c49-v2wc","MINI-6qv4-crh9-pj7p","MINI-7prw-57m6-wf4x","MINI-hq7v-jqq9-c3jh","MINI-mgcc-255g-7q73","MINI-p47g-v227-3rmj","MINI-wq68-f52f-353v","MINI-x4x2-9px5-v48w","UBUNTU-CVE-2026-65899"],"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 fails to reset Trusted Types policy state, allowing script execution via reused instances bound to unsafe policies.","user_interaction":"required","vuln_class":"security_feature_bypass"},"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-693","name":"Protection Mechanism Failure"}],"description":"DOMPurify 3.0.0 before 3.4.9 does not reset the retained Trusted Types policy when clearConfig() is called, so a DOMPurify instance reused across trust boundaries stays bound to a previously supplied TRUSTED_TYPES_POLICY. A later caller that requests RETURN_TRUSTED_TYPE output receives a TrustedHTML object created by the old (potentially unsafe) policy rather than a clean default, which can lead to script execution at a Trusted Types sink. Passing TRUSTED_TYPES_POLICY: null on the later call also does not clear the retained policy.","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 before 3.4.9 Trusted Types Policy State Contamination","id":"CVE-2026-65899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"DOMPurify before 3.4.8 Template Expression Injection via RETURN_DOM","id":"CVE-2026-65900"},"packages":[{"ecosystem":"npm","fixed":["3.4.9"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":null,"source":"GHSA-vxr8-fq34-vvx9"},{"ecosystem":"npm","fixed":["3.4.9"],"introduced":["0"],"last_affected":[],"package":"dompurify","purl":"pkg:npm/dompurify","source":"GHSA-vxr8-fq34-vvx9"}],"prev":{"headline":"DOMPurify before 3.4.11 Permanent Attribute Allowlist Pollution via setConfig","id":"CVE-2026-65898"},"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["cure53"]},"summary":"DOMPurify fails to reset Trusted Types policy state, allowing script execution via reused instances bound to unsafe policies.","url":"https://insights.sbomify.com/CVE-2026-65899/"}