<?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>Mon, 05 Oct 2026 17:36:03 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-355193</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-355193</link>
      <description>EUVD-2026-355193</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-355193</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54570</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54570</link>
      <description>&lt;p&gt;AngleSharp is a .NET library for parsing angle bracket based hyper-texts. Prior to 1.5.0, MathAnnotationXmlElement in AngleSharp/Mathml/Dom/Internal/MathAnnotationXmlElement.cs is not treated as an HTML integration point when its encoding attribute is text/html or application/xhtml+xml, causing Consume in AngleSharp/Html/Parser/HtmlDomBuilder.cs to route tokens through foreign-content parsing instead of HTML parsing. A sanitizer can therefore observe a different DOM from the browser that reparses the serialized output. An attacker can combine this namespace differential with markup-breaking characters in an attribute value so that an element hidden from the sanitizer becomes active script-capable HTML after browser reparse, resulting in mutation cross-site scripting. This issue is fixed in version 1.5.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AngleSharp is a .NET library for parsing angle bracket based hyper-texts. Prior to 1.5.0, MathAnnotationXmlElement in AngleSharp/Mathml/Dom/Internal/MathAnnotationXmlElement.cs is not treated as an HTML integration point when its encoding attribute is text/html or application/xhtml+xml, causing Consume in AngleSharp/Html/Parser/HtmlDomBuilder.cs to route tokens through foreign-content parsing instead of HTML parsing. A sanitizer can therefore observe a different DOM from the browser that reparses the serialized output. An attacker can combine this namespace differential with markup-breaking characters in an attribute value so that an element hidden from the sanitizer becomes active script-capable HTML after browser reparse, resulting in mutation cross-site scripting. This issue is fixed in version 1.5.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54570</guid>
    </item>
    <item>
      <title>GHSA-pgww-w46g-26qg — AngleSharp HTML5 Spec Compliance: mXSS via annotation-xml HTML Integration Point Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pgww-w46g-26qg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: AngleSharp&lt;/p&gt;
&lt;p&gt;### Summary
The HTML specification requires that a MathML `&amp;lt;annotation-xml&amp;gt;` element with `encoding=&amp;#34;text/html&amp;#34;` or `encoding=&amp;#34;application/xhtml+xml&amp;#34;` is treated as an HTML integration point. Content inside it must be parsed as HTML, not MathML.&lt;/p&gt;
&lt;p&gt;AngleSharp does not implement this correctly. As a result, the parser produces a DOM tree that differs from what a browser will build (different namespaces if `encoding=&amp;#34;text/html&amp;#34;` is not treated) when given the same serialized output. Two bugs combine to make this exploitable:&lt;/p&gt;
&lt;p&gt;- Missing HtmlTip flag: MathAnnotationXmlElement is never assigned NodeFlags.HtmlTip based on its encoding attribute, so the Consume() dispatch always routes tokens to Foreign() instead of Home() (HTML mode).
- Unescaped &amp;lt; &amp;gt; in attribute values: HtmlMarkupFormatter.WriteAttributeValue() does not escape &amp;lt; or &amp;gt; characters, only &amp;amp; and &amp;#34;. This allows injected markup to break out of attribute values on re-parse. _See [Escape &amp;#34;&amp;lt;&amp;#34; and &amp;#34;&amp;gt;&amp;#34; in attributes when serializing HTML #6235
](https://github.com/whatwg/html/issues/6235)_&lt;/p&gt;
&lt;p&gt;### Details
In `MathAnnotationXmlElement` (`AngleSharp/Mathml/Dom/Internal/MathAnnotationXmlElement.cs`):
```cs
// Current — HtmlTip is never set
: base(owner, TagNames.AnnotationXml, prefix, NodeFlags.Special | NodeFlags.Scoped)
```&lt;/p&gt;
&lt;p&gt;Because `HtmlTip` is absent, the token dispatch in `Consume()` always sends tokens to `Foreign()` when inside `annotation-xml`, regardless of the encoding attribute. The compensating check in `ForeignNormalTag…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; NuGet: AngleSharp&lt;/p&gt;
&lt;p&gt;### Summary
The HTML specification requires that a MathML `&amp;lt;annotation-xml&amp;gt;` element with `encoding=&amp;#34;text/html&amp;#34;` or `encoding=&amp;#34;application/xhtml+xml&amp;#34;` is treated as an HTML integration point. Content inside it must be parsed as HTML, not MathML.&lt;/p&gt;
&lt;p&gt;AngleSharp does not implement this correctly. As a result, the parser produces a DOM tree that differs from what a browser will build (different namespaces if `encoding=&amp;#34;text/html&amp;#34;` is not treated) when given the same serialized output. Two bugs combine to make this exploitable:&lt;/p&gt;
&lt;p&gt;- Missing HtmlTip flag: MathAnnotationXmlElement is never assigned NodeFlags.HtmlTip based on its encoding attribute, so the Consume() dispatch always routes tokens to Foreign() instead of Home() (HTML mode).
- Unescaped &amp;lt; &amp;gt; in attribute values: HtmlMarkupFormatter.WriteAttributeValue() does not escape &amp;lt; or &amp;gt; characters, only &amp;amp; and &amp;#34;. This allows injected markup to break out of attribute values on re-parse. _See [Escape &amp;#34;&amp;lt;&amp;#34; and &amp;#34;&amp;gt;&amp;#34; in attributes when serializing HTML #6235
](https://github.com/whatwg/html/issues/6235)_&lt;/p&gt;
&lt;p&gt;### Details
In `MathAnnotationXmlElement` (`AngleSharp/Mathml/Dom/Internal/MathAnnotationXmlElement.cs`):
```cs
// Current — HtmlTip is never set
: base(owner, TagNames.AnnotationXml, prefix, NodeFlags.Special | NodeFlags.Scoped)
```&lt;/p&gt;
&lt;p&gt;Because `HtmlTip` is absent, the token dispatch in `Consume()` always sends tokens to `Foreign()` when inside `annotation-xml`, regardless of the encoding attribute. The compensating check in `ForeignNormalTag…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pgww-w46g-26qg</guid>
    </item>
  </channel>
</rss>
