Bug 2526838 (CVE-2026-83611) - CVE-2026-83611 xmldom: xmldom: Malformed XML end tag parsing leads to content discard and security bypass
Summary: CVE-2026-83611 xmldom: xmldom: Malformed XML end tag parsing leads to content...
Keywords:
Status: NEW
Alias: CVE-2026-83611
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2527561 2527562 2527563 2527564 2527566 2527567 2527568 2527569
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-01 15:06 UTC by OSIDB Bzimport
Modified: 2026-09-02 15:38 UTC (History)
33 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-01 15:06:24 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, DOMParser.parseFromString() can silently accept an end tag such as </a\njunk>, close the element, and discard the trailing content. On 0.9.x, the lib/sax.js end-tag validator inherits the multiline flag from reg(), allowing the first line to satisfy the anchored XML ETag production; older lines have no equivalent residue validation. This parser differential can bypass a parse-before-trust well-formedness gate, although it does not inject the discarded content; onError on 0.9.x and errorHandler on 0.8.x are the relevant reporting interfaces. This issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fixed version is available for xmldom.


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