<?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>Thu, 08 Oct 2026 23:31:26 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-54267 — Angular Client Hydration DOM Clobbering &amp; Response-Cache Poisoning</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-54267</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; angular&lt;/p&gt;
&lt;p&gt;Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, to optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application&amp;#39;s runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a &amp;lt;script&amp;gt; tag with a predictable identifier. During client bootstrap, Angular recovers this state by looking up the element via document.getElementById(&amp;#39;ng-state&amp;#39;) and parsing its text content. Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering. If the application binds untrusted user input or CMS content to element properties such as id (e.g., &amp;lt;div [id]=&amp;#34;userInput&amp;#34;&amp;gt; or &amp;lt;a id=&amp;#34;ng-state&amp;#34;&amp;gt;) before the genuine &amp;lt;script&amp;gt; tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup. During hydration, when Angular calls document.getElementById(&amp;#39;ng-state&amp;#39;), the browser returns the attacker&amp;#39;s clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; angular&lt;/p&gt;
&lt;p&gt;Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.1, 21.2.17, and 20.3.25, to optimize client-side bootstrap in Server-Side Rendered (SSR) environments, Angular supports Hydration via provideClientHydration(). During SSR, Angular serializes the application&amp;#39;s runtime state (such as cached HttpClient responses) and outputs it into the HTML stream as a &amp;lt;script&amp;gt; tag with a predictable identifier. During client bootstrap, Angular recovers this state by looking up the element via document.getElementById(&amp;#39;ng-state&amp;#39;) and parsing its text content. Because the DOM element lookup for the state container is predictable and relies solely on the ID selector (ng-state), it is susceptible to DOM Clobbering. If the application binds untrusted user input or CMS content to element properties such as id (e.g., &amp;lt;div [id]=&amp;#34;userInput&amp;#34;&amp;gt; or &amp;lt;a id=&amp;#34;ng-state&amp;#34;&amp;gt;) before the genuine &amp;lt;script&amp;gt; tag is parsed by the browser, the attacker-controlled element takes precedence in the DOM lookup. During hydration, when Angular calls document.getElementById(&amp;#39;ng-state&amp;#39;), the browser returns the attacker&amp;#39;s clobbered element. Angular then attempts to parse the text content or attributes of this clobbered element as JSON. This vulnerability is fixed in 22.0.1, 21.2.17, and 20.3.25.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-54267</guid>
    </item>
  </channel>
</rss>
