https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 15:39:13 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-337193 EUVD-2026-337193 https://cve.radiocsirt.org/vuln/euvd-2026-337193 https://cve.radiocsirt.org/vuln/fkie_cve-2026-50556 <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&#39;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&#39;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&#39;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> <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&#39;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&#39;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&#39;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> https://cve.radiocsirt.org/vuln/fkie_cve-2026-50556 https://cve.radiocsirt.org/vuln/ghsa-gxx4-3xcv-f8qx <p><strong>Affected:</strong> npm: @angular/platform-server</p> <p>A Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`&#39;s DOM emulation dependency (`domino`) when serializing the content of `&lt;noscript&gt;` elements.</p> <p>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.</p> <p>However, `domino`&#39;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**.</p> <p>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&#39;s browser context, causing same-origin Cross-Site Scripting (XSS).</p> <p>### Impact</p> <p>This vulnerability allows an attacker to perform same-origin Cross-Site Scripting (XSS) attacks against any user visiting an SSR-rendered page that binds user-controlled data inside a `&lt;noscript&gt;` element. This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement.</p> <p>### Patched Versions</p> <p>- 22.0.0-rc.2 - 21.2.16…</p> <p><strong>Affected:</strong> npm: @angular/platform-server</p> <p>A Cross-Site Scripting (XSS) vulnerability exists in `@angular/platform-server`&#39;s DOM emulation dependency (`domino`) when serializing the content of `&lt;noscript&gt;` elements.</p> <p>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.</p> <p>However, `domino`&#39;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**.</p> <p>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&#39;s browser context, causing same-origin Cross-Site Scripting (XSS).</p> <p>### Impact</p> <p>This vulnerability allows an attacker to perform same-origin Cross-Site Scripting (XSS) attacks against any user visiting an SSR-rendered page that binds user-controlled data inside a `&lt;noscript&gt;` element. This can lead to session hijacking, credentials theft, unauthorized actions on behalf of users, and defacement.</p> <p>### Patched Versions</p> <p>- 22.0.0-rc.2 - 21.2.16…</p> https://cve.radiocsirt.org/vuln/ghsa-gxx4-3xcv-f8qx https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-50556 <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: angular.js, Ubuntu:Pro:18.04:LTS: angular.js, Ubuntu:Pro:20.04:LTS: angular.js, Ubuntu:22.04:LTS: angular.js, Ubuntu:24.04:LTS: angular.js, Ubuntu:25.10: angular.js, Ubuntu:26.04:LTS: angular.js</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&#39;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&#39;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&#39;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> <p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: angular.js, Ubuntu:Pro:18.04:LTS: angular.js, Ubuntu:Pro:20.04:LTS: angular.js, Ubuntu:22.04:LTS: angular.js, Ubuntu:24.04:LTS: angular.js, Ubuntu:25.10: angular.js, Ubuntu:26.04:LTS: angular.js</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&#39;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&#39;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&#39;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> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-50556 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1930 <p>Ein Angreifer kann mehrere Schwachstellen in Angular ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, einen Denial-of-Service-Zustand herbeizuführen, Daten zu manipulieren oder offenzulegen, Benutzer auf bösartige Websites umzuleiten oder Sitzungen zu kapern.</p> <p>Ein Angreifer kann mehrere Schwachstellen in Angular ausnutzen, um erweiterte Berechtigungen zu erlangen, beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, einen Denial-of-Service-Zustand herbeizuführen, Daten zu manipulieren oder offenzulegen, Benutzer auf bösartige Websites umzuleiten oder Sitzungen zu kapern.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1930