<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 04 Oct 2026 04:15:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-13731</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-13731</link>
      <description>bdu:2026-13731</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-13731</guid>
    </item>
    <item>
      <title>EUVD-2026-362541</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362541</link>
      <description>EUVD-2026-362541</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362541</guid>
    </item>
    <item>
      <title>fkie_cve-2026-83617</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-83617</link>
      <description>&lt;p&gt;xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-83617</guid>
    </item>
    <item>
      <title>GHSA-jxjr-3g7g-3944 — xmldom: requireWellFormed element/attribute name validation is bypassable via an embedded line terminator</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jxjr-3g7g-3944</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @xmldom/xmldom&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;An embedded line terminator bypasses the `requireWellFormed` serializer check for element and
attribute names. The check was added to fix GHSA-w2rr-34g9-rvrj and GHSA-4w3w-2rp5-g8jm; a name whose
first line is well-formed slips past it and is serialized verbatim, so the characters after the line
terminator break out of the start/end tag or attribute. Callers who enabled `requireWellFormed`
specifically to neutralize those name-injection issues remain exposed.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;xmldom builds every grammar production through a shared regexp builder that compiles with the `m`
flag. The anchored full-string matcher used for element and attribute names, `QName_exact =
reg(&amp;#39;^&amp;#39;, QName, &amp;#39;$&amp;#39;)`, therefore inherits `m`. When it is applied as `QName_exact.test(name)` against
an already-assembled node name, the `m` flag makes `$` match at an interior line terminator, so the
matcher accepts any value in which **at least one line** is a valid `QName`; the other lines are never
constrained. A payload whose first line is a valid `QName`, followed by a line terminator and breakout
markup, is what yields a working injection.&lt;/p&gt;
&lt;p&gt;The serializer emits the accepted name verbatim into element start/end tags and attribute names, so
the bytes after the line terminator break out of the intended syntactic position. The check is
reached whenever a caller serializes, with `requireWellFormed: true`, a node whose name was set
through programmatic DOM construction (`createElement`, `createElementNS`, `…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @xmldom/xmldom&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;An embedded line terminator bypasses the `requireWellFormed` serializer check for element and
attribute names. The check was added to fix GHSA-w2rr-34g9-rvrj and GHSA-4w3w-2rp5-g8jm; a name whose
first line is well-formed slips past it and is serialized verbatim, so the characters after the line
terminator break out of the start/end tag or attribute. Callers who enabled `requireWellFormed`
specifically to neutralize those name-injection issues remain exposed.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;xmldom builds every grammar production through a shared regexp builder that compiles with the `m`
flag. The anchored full-string matcher used for element and attribute names, `QName_exact =
reg(&amp;#39;^&amp;#39;, QName, &amp;#39;$&amp;#39;)`, therefore inherits `m`. When it is applied as `QName_exact.test(name)` against
an already-assembled node name, the `m` flag makes `$` match at an interior line terminator, so the
matcher accepts any value in which **at least one line** is a valid `QName`; the other lines are never
constrained. A payload whose first line is a valid `QName`, followed by a line terminator and breakout
markup, is what yields a working injection.&lt;/p&gt;
&lt;p&gt;The serializer emits the accepted name verbatim into element start/end tags and attribute names, so
the bytes after the line terminator break out of the intended syntactic position. The check is
reached whenever a caller serializes, with `requireWellFormed: true`, a node whose name was set
through programmatic DOM construction (`createElement`, `createElementNS`, `…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jxjr-3g7g-3944</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-83617</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-83617</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-xmldom, Ubuntu:22.04:LTS: node-xmldom, Ubuntu:24.04:LTS: node-xmldom, Ubuntu:26.04:LTS: node-xmldom&lt;/p&gt;
&lt;p&gt;xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: node-xmldom, Ubuntu:22.04:LTS: node-xmldom, Ubuntu:24.04:LTS: node-xmldom, Ubuntu:26.04:LTS: node-xmldom&lt;/p&gt;
&lt;p&gt;xmldom is a pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module. From 0.9.11 until 0.9.12, the requireWellFormed: true element and attribute name checks use the anchored QName_exact expression produced by reg() in lib/grammar.js, which inherits the multiline flag. A name with a valid first line followed by U+000A, U+000D, U+2028, or U+2029 and breakout markup therefore passes validation and is emitted verbatim in element start and end tags or attribute names. This bypasses the strict-serialization checks introduced for the earlier element-name and attribute-name injection advisories, while the default serialization path remains outside the strict guarantee. This issue is fixed in @xmldom/xmldom version 0.9.12.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-83617</guid>
    </item>
  </channel>
</rss>
