{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-65904 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-65904 is a low-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-65904 and fix it if it is affected.\n\nWhat it is: CVE-2026-65904 is a low-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-65904 exists.\n\nAffected product: cure53 DOMPurify. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-65904/ (Markdown: https://insights.sbomify.com/CVE-2026-65904/index.md)","id":"CVE-2026-65904","markdown":"https://insights.sbomify.com/CVE-2026-65904/index.md","name":"CVE-2026-65904","record":{"aliases":["DEBIAN-CVE-2026-65904","GHSA-4w3q-35jp-p934","UBUNTU-CVE-2026-65904"],"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":"DOMPurify fails to sanitize cross-realm DOM elements in IN_PLACE mode, allowing attackers to inject XSS payloads.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"dompurify","vendor":"cure53"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"DOMPurify through 3.3.3 fails to sanitize DOM elements passed via IN_PLACE mode when the element originates from a different window/realm (e.g., an iframe's contentDocument). A cross-realm instanceof check in the private _isNode() function returns false for foreign-realm nodes, causing DOMPurify to stringify the element (yielding '[object HTMLDivElement]'), silently reset IN_PLACE to false, and return the unsanitized element unchanged with any XSS payloads intact.","ecosystems":[],"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 through 3.3.3 Cross-Site Scripting via IN_PLACE mode","id":"CVE-2026-65904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Tomcat: Limited replay attack possible with DIGEST authentication","id":"CVE-2026-65905"},"packages":[],"prev":{"headline":"DOMPurify before 3.4.0 ADD_TAGS Function Bypasses FORBID_TAGS","id":"CVE-2026-65903"},"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":"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-07-24","vendors":["cure53"]},"summary":"DOMPurify fails to sanitize cross-realm DOM elements in IN_PLACE mode, allowing attackers to inject XSS payloads.","url":"https://insights.sbomify.com/CVE-2026-65904/"}