Vulnerabilities in pkg:npm/@xmldom/xmldom
PACKAGECVE-2026-83616 is a HIGH processing instruction target injection bypasses vulnerability (CWE-91: XML Injection (aka Blind XPath Injection)) affecting xmldom libraries in the npm ecosystem. The issue involves processing instruction target injection bypasses requirewellformed. Remediation is available by upgrading affected packages to version 0.8.15, 0.9.12.
pkg:npm/@xmldom/xmldom
Vulnerability advisories affecting package pkg:npm/@xmldom/xmldom. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-c7q8-3ch8-vqpv | CVE-2026-83616 | HIGH | xmldom: Processing Instruction Target Injection Bypasses requireWellFormed |
| GHSA-jxjr-3g7g-3944 | CVE-2026-83617 | HIGH | xmldom: requireWellFormed element/attribute name validation is bypassable via an embedded line terminator |
| GHSA-27p8-2357-5qqv | CVE-2026-83608 | HIGH | xmldom: DocType `name` Injection Bypasses requireWellFormed |
| GHSA-3px3-54cx-rmw9 | CVE-2026-83609 | HIGH | xmldom: Creation-time XML Name/QName validation is bypassable via an embedded line terminator, allowing injection on the default serialization path |
| GHSA-vr34-hp96-76pp | CVE-2026-83618 | HIGH | xmldom: requireWellFormed DocType publicId/systemId validation is bypassable via an embedded line terminator |
| GHSA-6h8r-xr42-gp59 | CVE-2026-83611 | MODERATE | xmldom: Parser silently accepts a not-well-formed end tag whose name is followed by a line break and trailing content |
| GHSA-8344-3jmq-59r6 | CVE-2026-83613 | HIGH | xmldom: Quadratic-time attribute deduplication |
| GHSA-x4fp-j954-r2f4 | CVE-2026-83619 | HIGH | xmldom: End-tag Whitespace-Trim Regex ReDoS — quadratic backtracking in the 0.8.x end-tag parser |
| GHSA-965w-775f-mr7g | CVE-2026-83615 | HIGH | xmldom: Quadratic-memory consumption |
| GHSA-93r5-fhx6-vmg9 | CVE-2026-83614 | HIGH | xmldom: Quadratic-time parsing via the malformed-input recovery path — `parseElementStartPart` re-scan and `normalize()` adjacent-text merge |
| GHSA-6mj3-qw4j-hgrw | CVE-2026-83612 | HIGH | xmldom: HTML raw-text closing-tag case mismatch causes output amplification |
| GHSA-g53g-w8rj-fmg7 | CVE-2026-83606 | HIGH | xmldom PI grammar regex ReDoS: quadratic backtracking on unterminated processing instructions |
| GHSA-w2rr-34g9-rvrj | CVE-2026-83607 | HIGH | xmldom: Element name injection via createElement() bypasses requireWellFormed |
| GHSA-4w3w-2rp5-g8jm | CVE-2026-83605 | HIGH | xmldom: Attribute name injection via setAttribute() bypasses requireWellFormed |
| GHSA-6gmq-8vp8-gcm6 | CVE-2026-83610 | MODERATE | xmldom: XML fragment injection via invalid EntityReference.nodeName during requireWellFormed serialization |
| GHSA-2v35-w6hq-6mfw | CVE-2026-41673 | HIGH | xmldom: Uncontrolled recursion in XML serialization leads to DoS |
| GHSA-f6ww-3ggp-fr8h | CVE-2026-41674 | HIGH | xmldom has XML injection through unvalidated DocumentType serialization |
| GHSA-x6wf-f3px-wcqx | CVE-2026-41675 | HIGH | xmldom has XML node injection through unvalidated processing instruction serialization |
| GHSA-j759-j44w-7fr8 | CVE-2026-41672 | HIGH | xmldom has XML node injection through unvalidated comment serialization |
| GHSA-wh4c-j3r5-mjhp | CVE-2026-34601 | HIGH | xmldom: XML injection via unsafe CDATA serialization allows attacker-controlled markup insertion |
| GHSA-5fg8-2547-mr8q | CVE-2021-32796 | MODERATE | Misinterpretation of malicious XML input |
| GHSA-9pgh-qqpf-7wqj | CVE-2022-37616 | CRITICAL | Withdrawn: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in @xmldom/xmldom and xmldom |
| GHSA-crh6-fp67-6883 | CVE-2022-39353 | CRITICAL | xmldom allows multiple root nodes in a DOM |
CVE-2026-83616 at a Glance
How to Fix CVE-2026-83616
To remediate this vulnerability, upgrade all affected xmldom dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @xmldom/xmldom@0.8.15
npm install @xmldom/xmldom@0.9.12
npm install xmldom@Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @xmldom/xmldom
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-83616, inspect your project dependencies using npm:
npm ls @xmldom/xmldom
Analyze the terminal output to locate any version of xmldom in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.8.15), your application is affected.
Note: The npm ls @xmldom/xmldom command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-91: XML Injection (aka Blind XPath Injection), where the product does not properly neutralize special elements that are used in xml, allowing attackers to modify the syntax, content, or commands of the xml before it is processed by an end system. In xmldom, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-83616 Affected xmldom Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@xmldom/xmldom
|
npm |
≥ 0.7.0
< 0.8.15
|
0.8.15
|
|
@xmldom/xmldom
|
npm |
≥ 0.9.0
< 0.9.12
|
0.9.12
|
|
xmldom
|
npm |
≤ 0.6.0
|
|
References
Frequently Asked Questions
What is CVE-2026-83616?
Which xmldom versions are affected?
What version fixes CVE-2026-83616?
Is @xmldom/xmldom affected?
Is xmldom affected?
What CWE is associated with CVE-2026-83616?
How can I check npm dependencies for CVE-2026-83616?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-c7q8-3ch8-vqpv",
"modified" : "2026-09-08T21:03:28Z",
"published" : "2026-09-08T21:03:28Z",
"aliases" : [ "CVE-2026-83616" ],
"summary" : "xmldom: Processing Instruction Target Injection Bypasses requireWellFormed",
"details" : "## Summary\n\n`Document.createProcessingInstruction()` in `@xmldom/xmldom` performs no validation on the `target` parameter. The `requireWellFormed: true` serializer option validates only for `:` in the target and a case-insensitive `xml` prefix, but does not check for `>` characters. A `>` in the target breaks the processing instruction boundary (`<?...?>`), allowing injection of arbitrary content into the serialized XML output.\n\n## Details\n\n`Document.createProcessingInstruction(target, data)` at `lib/dom.js` around line 2413 accepts any string as the `target` parameter and stores it on the PI node without validation.\n\nDuring serialization, the `requireWellFormed` code path (around line 3286) performs two checks on PI targets:\n\n1. Rejects targets containing `:` (namespace prefix check)\n2. Rejects targets matching `xml` case-insensitively (reserved prefix)\n\nHowever, it does NOT validate that the target conforms to the XML Name production, and critically does NOT check for `>` characters. Since processing instructions are serialized as `<?target data?>`, a `>` in the target prematurely closes the PI, causing the remaining content to be interpreted as document content by any downstream XML parser.\n\n### Root Cause\n\n1. `createProcessingInstruction()` performs no validation on `target`\n2. The serializer's `requireWellFormed` check is incomplete -- it only checks for `:` and `xml`, missing characters that break PI syntax (`>`, `?`, whitespace)\n3. The serializer emits the target verbatim: `<?${target} ${data}?>`\n\n## Proof of Concept\n\n```javascript\nconst { DOMImplementation, XMLSerializer } = require('@xmldom/xmldom');\n\nconst impl = new DOMImplementation();\nconst serializer = new XMLSerializer();\nconst doc = impl.createDocument(null, 'root', null);\n\n// PI target containing > breaks the PI boundary\nconst pi = doc.createProcessingInstruction('a>', 'data');\ndoc.documentElement.appendChild(pi);\n\nconst output = serializer.serializeToString(doc, { requireWellFormed: true });\nconsole.log(output);\n// Output: <root><?a> data?></root>\n//\n// The > in the target closes the PI prematurely.\n// A downstream XML parser sees:\n// - Processing instruction: <?a?> (target \"a\", no data)\n// - Text content: \" data?>\"\n//\n// requireWellFormed: true did NOT prevent the injection.\n```\n\n### Injecting elements via PI target\n\n```javascript\nconst pi2 = doc.createProcessingInstruction(\n 'a?><script xmlns=\"http://www.w3.org/1999/xhtml\">alert(1)</script><?b',\n ''\n);\ndoc.documentElement.appendChild(pi2);\n\nconst output2 = serializer.serializeToString(doc, { requireWellFormed: true });\nconsole.log(output2);\n// Output includes:\n// <?a?><script xmlns=\"http://www.w3.org/1999/xhtml\">alert(1)</script><?b ?>\n//\n// The injected <script> element is valid XHTML that a browser would execute.\n```\n\n## Impact\n\nApplications that create processing instructions with user-controlled target strings and serialize the result are vulnerable to XML injection. This enables:\n\n- **XML structure injection**: Breaking the PI boundary to inject arbitrary elements, text, or additional processing instructions into the output\n- **XSS via XHTML**: If the serialized output is served as XHTML or processed by a browser-based XML parser, injected script elements will execute\n- **XXE chain**: Injected DOCTYPE declarations or entity references could trigger XXE in downstream XML parsers that consume the output\n- **requireWellFormed bypass**: The existing well-formedness checks are incomplete and provide a false sense of security\n\n## Fix Applied\n\nUnder `requireWellFormed`, the serializer validates a processing-instruction target as an XML `NCName` (a `Name` with no colon) and rejects a case-insensitive `xml`, throwing `InvalidStateError` when the target is ill-formed — so a `>`, `?`, or whitespace in the target is now refused.\\\nOn 0.9.12 this replaces an earlier check that already rejected a colon or `xml`, so the no-colon rule is preserved.\\\n0.8.15 had no processing-instruction target check at all, so the whole target validation is new there.\\\nNon-breaking and opt-in. See the [XML `Name` production](https://www.w3.org/TR/xml/#NT-Name).\n> **⚠ Opt-in required.** Protection is not automatic. Existing serialization calls remain\n> vulnerable unless `{ requireWellFormed: true }` is explicitly passed. Applications that\n> serialize untrusted DOM content should audit all `serializeToString()` call sites and add it.\n\n### Proof of Concept - fixed path\n\n```javascript\nconst { DOMImplementation, XMLSerializer } = require('@xmldom/xmldom');\n\nconst impl = new DOMImplementation();\nconst serializer = new XMLSerializer();\nconst doc = impl.createDocument(null, 'root', null);\n\n// PI target containing > breaks the PI boundary\nconst pi = doc.createProcessingInstruction('a>', 'data');\ndoc.documentElement.appendChild(pi);\n\n// Default path: emits the ill-formed target verbatim.\nconsole.log(serializer.serializeToString(doc));\n// Output: <root><?a> data?></root>\n\n// Opt-in path: the target check now rejects the break-out character.\ntry {\n serializer.serializeToString(doc, { requireWellFormed: true });\n} catch (e) {\n console.log(e.name); // InvalidStateError\n}\n```\n\n### Why the default stays verbatim\n\nW3C DOM Parsing's require-well-formed flag defaults to false, and the browser `XMLSerializer` emits the target verbatim in that default mode. Unconditionally throwing on an ill-formed PI target would diverge from that platform behavior and would be an unjustified breaking change, so the stricter validation is gated behind `{ requireWellFormed: true }`. (See the [W3C XML Name production](https://www.w3.org/TR/xml/#NT-Name) and [XML Processing Instructions](https://www.w3.org/TR/xml/#sec-pi).)\n\n### Residual limitation\n\nThe default serialization path still emits the ill-formed target verbatim -- only the opt-in `requireWellFormed` path is protected. Creation-time validation of the `target` in `createProcessingInstruction()` is breaking and is deferred to the next breaking release, tracked at [xmldom/xmldom#1073](https://github.com/xmldom/xmldom/issues/1073).",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@xmldom/xmldom"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.7.0"
}, {
"fixed" : "0.8.15"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.8.14"
}
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@xmldom/xmldom"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0.9.0"
}, {
"fixed" : "0.9.12"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.9.11"
}
}, {
"package" : {
"ecosystem" : "npm",
"name" : "xmldom"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "0.6.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/security/advisories/GHSA-c7q8-3ch8-vqpv"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-83616"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/pull/1071"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/pull/1072"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/commit/1cde3e31a07c41c87cfd368d6946aa477f16b4f9"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/commit/3b694872bcb5c7e3cbadba961a4be2488750ce5b"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/xmldom/xmldom"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/releases/tag/0.8.15"
}, {
"type" : "WEB",
"url" : "https://github.com/xmldom/xmldom/releases/tag/0.9.12"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-91" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-08T21:03:28Z",
"nvd_published_at" : "2026-09-01T15:17:40Z"
}
}