<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T20:20:17.625309+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-50556</id>
    <title>CVE-2026-50556 — Angular: Missing `&lt;noscript&gt;` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR</title>
    <updated>2026-10-06T20:20:17.641371+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> angular, Red Hat Enterprise Linux 8, Red Hat Fuse 7</p>
<p>Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25, a Cross-Site Scripting (XSS) vulnerability exists in @angular/platform-server's DOM emulation dependency (domino) when serializing the content of &lt;noscript&gt; elements. When rendering dynamic text content inside a &lt;noscript&gt; element via template bindings (such as {{ value }} or [textContent]), the template engine expects the browser to render the content safely. Under Server-Side Rendering (SSR), domino is configured with scripting enabled, meaning &lt;noscript&gt; is treated as a raw-text element. However, domino's serializer completely omitted &lt;noscript&gt; from the list of raw-text elements requiring closing-tag escaping during DOM serialization. As a result, any occurrence of &lt;/noscript&gt; in the bound dynamic text was never escaped under any circumstances. The unescaped closing tag was serialized directly into the output HTML (e.g. &lt;noscript&gt;&lt;/noscript&gt;&lt;script&gt;alert(1)&lt;/script&gt;&lt;/noscript&gt;). When parsed by a browser, it closes the &lt;noscript&gt; block early, allowing the injected &lt;script&gt; block to execute in the user's browser context, causing same-origin Cross-Site Scripting (XSS). This vulnerability is fixed in 22.0.0-rc.2, 21.2.16, 20.3.24, and 19.2.25.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-50556"/>
  </entry>
</feed>
