xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0 until 0.9.12, the shared reg() builder in lib/grammar.js compiles the anchored QName_exact validator with the multiline flag, so ^ and $ validate only one line instead of the complete name. createElementNS, createAttributeNS, createDocumentType, and createAttribute consequently accept a malformed XML name whose first line is valid and whose later text injects markup when serialized through either the default path or requireWellFormed: true. The triggering ECMAScript line terminators are U+000A, U+000D, U+2028, and U+2029. This issue is fixed in @xmldom/xmldom version 0.9.12.
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0 until 0.9.12, the shared reg() builder in lib/grammar.js compiles the anchored QName_exact validator with the multiline flag, so ^ and $ validate only one line instead of the complete name. createElementNS, createAttributeNS, createDocumentType, and createAttribute consequently accept a malformed XML name whose first line is valid and whose later text injects markup when serialized through either the default path or requireWellFormed: true. The triggering ECMAScript line terminators are U+000A, U+000D, U+2028, and U+2029. This issue is fixed in @xmldom/xmldom version 0.9.12.
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.0 until 0.9.12, the shared reg() builder in lib/grammar.js compiles the anchored QName_exact validator with the multiline flag, so ^ and $ validate only one line instead of the complete name. createElementNS, createAttributeNS, createDocumentType, and createAttribute consequently accept a malformed XML name whose first line is valid and whose later text injects markup when serialized through either the default path or requireWellFormed: true. The triggering ECMAScript line terminators are U+000A, U+000D, U+2028, and U+2029. This issue is fixed in @xmldom/xmldom version 0.9.12.
## Summary
An embedded line terminator bypasses xmldom's always-on, WHATWG-mandated creation-time name
validation. `createElementNS`, `createAttributeNS`, `createDocumentType`, and `createAttribute` should
reject a malformed qualified name with `InvalidCharacterError`, but a name whose first line is
well-formed slips through and enters the DOM. On serialization it is emitted verbatim, so the
characters after the line terminator inject markup into the output. The injection reaches the default
serialization path, and enabling `requireWellFormed` does not prevent it.
## Details
`createElementNS`, `createAttributeNS`, and `createDocumentType` route through `validateQualifiedName`,
and `createAttribute` performs the analogous check; each validates the name with
`g.QName_exact.test(name)`. `QName_exact = reg('^', QName, '$')` inherits the `m` flag from xmldom's
shared regexp builder, so the matcher accepts any name whose first line is a valid `QName` and leaves
the remaining lines unconstrained (see Root Cause).
### Root Cause
1. A shared regexp builder compiles anchored productions with the `m` flag.
2. `^…$` under `m` are line anchors, not string anchors.
3. `validateQualifiedName` / `createAttribute` validate with `.test()` against such a production, so a
line terminator followed by breakout markup passes and the malformed name is stored.
The triggering line terminators are the ECMAScript `LineTerminator` set: U+000A, U+000D, U+2028, U+2029.
## Proof of Concept
```js
const { DOMImplementation, XMLSerializer } = require('@xmldom/xmldom');
const impl = new DOMImplementation();
const doc = impl.createDocument('urn:x', 'root', null);
const el = doc.createElementNS('urn:x', 'a\n><script>x</script'); // ACCEPTED (no throw)
doc.documentElement.appendChild(el);
// DEFAULT serialization — requireWellFormed NOT set:
console.log(new XMLSerializer().serializeToString(doc));
// Observed: <root xmlns="urn:x"><a
// ><script>x</script/></root> <-- injected element on the default path
// Control: createElementNS('urn:x', 'bad>name') throws InvalidCharacterError, confirming the check is
// active and specifically bypassed by the line terminator.
```
## Impact
- **Bypass of the always-on WHATWG creation-time name validation** (`InvalidCharacterError`): a
malformed name the standard requires be rejected at creation is instead admitted to the DOM.
- **Markup / structure injection.** An application relying on the `create*` APIs to reject malformed
names (the standard behavior) as a trust boundary is exposed; where the serialized output reaches an
HTML context, downstream XSS.
- **No serializer option mitigates it.** The admitted name is emitted verbatim under *both* the default
path and `requireWellFormed: true` — the strict serializer shares the same `m`-flagged blind spot
(the subject of the sibling serializer advisories) — so the bypassed creation-time check was the only
layer that could have stopped it. Demonstrated for all four `create*` sites in
`poc_creation_strict_serialization_bypass.cjs`.
## Fix Applied
`createElementNS`, `createAttributeNS`, `createDocumentType`, and `createAttribute` now reject a name
containing a line terminator with `InvalidCharacterError` — the same result they already give for
other malformed names — because name validation now applies to the whole string. The
`requireWellFormed` serializer's name checks are corrected by the same change. The fix is
non-breaking: such a name was already invalid, and no previously-accepted well-formed name is affected.
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Sep 1, 2026, 2:29:40 PM
dateUpdated: Sep 1, 2026, 6:10:19 PM
1 related source bulletins · separate from aliases
WID-SEC-W-2026-3596: IBM App Connect Enterprise: Mehrere Schwachstellen
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Deferred
Weakness classifications: CWE-91 · CWE-625
Original publisher date fields
published: 2026-09-01T15:17:38.953
lastModified: 2026-09-08T21:11:31.703
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.