Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 01 Sep 2026 22:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Xmldom
Xmldom xmldom |
|
| Vendors & Products |
Xmldom
Xmldom xmldom |
|
| Metrics |
ssvc
|
Tue, 01 Sep 2026 14:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.14 and 0.9.11, and in xmldom version 0.6.0 and earlier, Document.createElement(tagName) stores an unvalidated element name and XMLSerializer.serializeToString() emits that name verbatim. The requireWellFormed: true path did not validate the element qualified name or synthesized xmlns:PREFIX declaration, so attacker-controlled tag names could inject attributes, elements, or processing instructions into serialized XML or HTML and could cause cross-site scripting when browser-consumed. The unchecked values violate the XML QName constraint, and default serialization and creation-time createElement() behavior remain permissive. This issue is fixed in @xmldom/xmldom versions 0.8.14 and 0.9.11; no fixed version is available for xmldom. | |
| Title | xmldom: Element name injection via createElement() bypasses requireWellFormed | |
| Weaknesses | CWE-91 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-01T15:28:37.947Z
Reserved: 2026-08-31T20:36:25.743Z
Link: CVE-2026-83607
Updated: 2026-09-01T15:28:33.075Z
Status : Received
Published: 2026-09-01T15:17:38.650
Modified: 2026-09-01T16:17:26.413
Link: CVE-2026-83607
No data.
OpenCVE Enrichment
Updated: 2026-09-01T16:45:04Z
-
CWE-91
XML Injection (aka Blind XPath Injection)