<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:xmldom_project:xmldom:0.9.11:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3axmldom_projectxmldom0.9.11/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 08 Sep 2026 21:50:46 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3axmldom_projectxmldom0.9.11/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>xmldom requireWellFormed Serialization Bypass</title><link>https://feed.craftedsignal.io/briefs/2026-09-xmldom-injection-bypass/</link><pubDate>Tue, 08 Sep 2026 21:50:46 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-09-xmldom-injection-bypass/</guid><description>The xmldom serializer fails to properly validate element and attribute names when the requireWellFormed option is enabled, allowing attackers to inject arbitrary markup via line-terminated strings.</description><content:encoded><![CDATA[<p>The xmldom package is vulnerable to a security bypass affecting the <code>requireWellFormed</code> option in <code>XMLSerializer</code>. The issue stems from the use of a regular expression compiled with the <code>m</code> (multiline) flag to validate XML element and attribute names. Under these conditions, the <code>$</code> anchor matches line terminators rather than the end of the entire string. Consequently, the validator only verifies that the first line of an element or attribute name is well-formed, allowing any content following a line terminator (U+000A, U+000D, U+2028, or U+2029) to be serialized verbatim.</p>
<p>This vulnerability impacts applications that rely on the <code>requireWellFormed: true</code> option as a defense against name-injection attacks, such as those identified in GHSA-w2rr-34g9-rvrj and GHSA-4w3w-2rp5-g8jm. Attackers capable of influencing element or attribute names during programmatic DOM construction can bypass these safety checks to inject arbitrary XML or HTML. If the resulting output is rendered in a browser, this injection can lead to Cross-Site Scripting (XSS).</p>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows for the bypass of previously implemented security mitigations for XML name injection. Successful exploitation enables the injection of arbitrary markup into serialized XML strings. When these strings are rendered in web contexts, attackers can achieve Cross-Site Scripting (XSS), potentially leading to unauthorized data access, session hijacking, or other client-side malicious activity. This affects all downstream applications that trust <code>xmldom</code> to sanitize output through the <code>requireWellFormed</code> serializer option.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the <code>xmldom</code> dependency to a version that patches CVE-2026-83617.</li>
<li>Audit all application codebases for instances of <code>XMLSerializer.serializeToString()</code> that utilize the <code>{ requireWellFormed: true }</code> option to ensure they are updated to the corrected library version.</li>
<li>For applications handling untrusted user input, implement server-side validation of element and attribute names before DOM construction to ensure they strictly conform to XML QName specifications.</li>
<li>Ensure that serialized output containing user-controlled data is properly escaped or sanitized before rendering it in browser-based contexts to mitigate residual XSS risks.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>injection</category><category>xss</category><category>library-vulnerability</category></item></channel></rss>