xmldom: HTML raw-text closing-tag case mismatch causes output amplification
CVE-2026-83612GHSA-6mj3-qw4j-hgrw
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (@xmldom/xmldom 0.9.12), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @xmldom/xmldom
- Affected
- >= 0.9.0-beta.1, <= 0.9.11
- Fixed in
- 0.9.12
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-6mj3-qw4j-hgrw lists affected ranges: npm @xmldom/xmldom >=0.9.0-beta.1 <=0.9.11
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-6mj3-qw4j-hgrw lists affected ranges: npm @xmldom/xmldom >=0.9.0-beta.1 <0.9.12 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-83612: 0.52% estimated exploitation activity in the next 30 days; percentile 44.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary In HTML mode (text/html), a raw-text element (script, style, textarea, title) whose closing tag differs in case from its opening tag (e.g. </ScRiPt for <script) is mishandled by the parser, producing quadratic (O(n²)) output growth — a small crafted document parses and serializes into output orders of magnitude larger, exhausting CPU and memory. A modest input of tens of KB can therefore cause a denial of service in any service that parses untrusted HTML with xmldom. Only HTML mode is affected. Details The parser calls parseHtmlSpecialContent for each raw-text element in HTML mode, matched via isHTMLRawTextElement / isHTMLEscapableRawTextElement (so all four types — script, style, textarea, title — are in scope). It searches for the element's closing tag with source.indexOf('</' + tagName + '', elStartEnd), a byte-for-byte case-sensitive match. A mixed-case closing tag never matches, so the search returns -1, and the following source.substring(elStartEnd + 1, -1) extracts…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 4 · amended ·
Amended from ghsa record GHSA-6mj3-qw4j-hgrw
- Revision 3 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 2 · amended ·
Amended from osv record GHSA-6mj3-qw4j-hgrw
- Revision 1 · created ·
Published from ghsa record GHSA-6mj3-qw4j-hgrw
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-83612 Advisory: xmldom: HTML raw-text closing-tag case mismatch causes output amplification IDs: CVE-2026-83612, GHSA-6mj3-qw4j-hgrw Record: https://patchnext.com/advisories/cve-2026-83612 (revision 4, source checked 26 Oct 2026, 13:02 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.7) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: @xmldom/xmldom 0.9.12. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @xmldom/xmldom: affected >= 0.9.0-beta.1, <= 0.9.11; fixed in 0.9.12 ## Suggested inspection (read-only) - `npm ls @xmldom/xmldom --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @xmldom/xmldom. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-6mj3-qw4j-hgrw (GitHub-reviewed advisory GHSA-6mj3-qw4j-hgrw lists affected ranges: npm @xmldom/xmldom >=0.9.0-beta.1 <=0.9.11) - Verified: https://osv.dev/vulnerability/GHSA-6mj3-qw4j-hgrw (OSV record GHSA-6mj3-qw4j-hgrw lists affected ranges: npm @xmldom/xmldom >=0.9.0-beta.1 <0.9.12 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…