{"answers":{"affected":"2 open source packages ship an affected version, including @xmldom/xmldom.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-83617 exists.","fix":"Upgrade @xmldom/xmldom to 0.9.12 or later.","what":"CVE-2026-83617 is a high-severity vulnerability in @xmldom xmldom, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-83617 and fix it if it is affected.\n\nWhat it is: CVE-2026-83617 is a high-severity vulnerability in @xmldom xmldom, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-83617 exists.\n\nAffected packages and fixed versions:\n- @xmldom/xmldom (npm): affected from 0.9.11; fixed in 0.9.12\n- @xmldom/xmldom (npm): affected from 0.9.11; fixed in 0.9.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-83617/ (Markdown: https://insights.sbomify.com/CVE-2026-83617/index.md)","id":"CVE-2026-83617","markdown":"https://insights.sbomify.com/CVE-2026-83617/index.md","name":"CVE-2026-83617","record":{"aliases":["DEBIAN-CVE-2026-83617","GHSA-jxjr-3g7g-3944","ROOT-APP-NPM-CVE-2026-83617","UBUNTU-CVE-2026-83617"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript XML library","requires_auth":"none","summary":"Attackers can bypass XML well-formedness checks to inject markup, potentially leading to code execution or security bypasses in applications using xmldom.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-91","name":"XML Injection"},{"id":"CWE-625","name":"Permissive Regular Expression"}],"description":"xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.","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":"xmldom: requireWellFormed element/attribute name validation is bypassable via an embedded line terminator","id":"CVE-2026-83617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"xmldom: requireWellFormed DocType publicId/systemId validation is bypassable via an embedded line terminator","id":"CVE-2026-83618"},"packages":[{"ecosystem":"npm","fixed":["0.9.12"],"introduced":["0.9.11"],"last_affected":[],"package":"@xmldom/xmldom","purl":null,"source":"GHSA-jxjr-3g7g-3944"},{"ecosystem":"npm","fixed":["0.9.12"],"introduced":["0.9.11"],"last_affected":[],"package":"@xmldom/xmldom","purl":"pkg:npm/%40xmldom/xmldom","source":"GHSA-jxjr-3g7g-3944"}],"prev":{"headline":"xmldom: Processing Instruction Target Injection Bypasses requireWellFormed","id":"CVE-2026-83616"},"products":["xmldom"],"published":"2026-09-01","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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-01","vendors":["@xmldom","xmldom"]},"summary":"Attackers can bypass XML well-formedness checks to inject markup, potentially leading to code execution or security bypasses in applications using xmldom.","url":"https://insights.sbomify.com/CVE-2026-83617/"}