Bug 2526816 (CVE-2026-83608) - CVE-2026-83608 xmldom: @xmldom/xmldom: xmldom: XML Markup Injection via DocType Name Bypass
Summary: CVE-2026-83608 xmldom: @xmldom/xmldom: xmldom: XML Markup Injection via DocTy...
Keywords:
Status: NEW
Alias: CVE-2026-83608
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2527271 2527274 2527281 2527283 2527284 2527285
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 14:46 UTC by OSIDB Bzimport
Modified: 2026-09-02 07:56 UTC (History)
33 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-01 14:46:01 UTC
xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. Prior to @xmldom/xmldom versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, the DOCUMENT_TYPE_NODE branch in lib/dom.js validates publicId, systemId, and internalSubset under requireWellFormed: true but emits DocumentType.name verbatim. A name containing > or whitespace can terminate the <!DOCTYPE ...> declaration and inject sibling markup; the value can be supplied through createDocumentType() on the 0.8.x and unscoped lines or through a direct DocumentType.name property write on every affected line. The default path and legacy creation-time behavior remain permissive, while the vulnerable strict path fails to enforce an XML Name. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.

Comment 1 Yadnyawalk Tale 2026-09-02 07:37:56 UTC
CVSS Justification:

AC:H because the attacker must control DocumentType.name (often via direct property write), which parse-only XML flows don't reach. I:L instead of I:H and UI:R added because impact is narrow markup injection / conditional XSS, not general integrity compromise.


Note You need to log in before you can comment on or make changes to this bug.