<?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>Tue, 17 Nov 2026 05:41:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-405802</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-405802</link>
      <description>EUVD-2026-405802</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-405802</guid>
    </item>
    <item>
      <title>fkie_cve-2026-126361</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126361</link>
      <description>&lt;p&gt;Astro is a web framework for content-driven websites. Prior to 7.4.5, Astro rendered a string used as a dynamic element name as raw HTML after applying an incomplete character filter. A / in the string could make an HTML parser treat the remainder as attributes, allowing untrusted element-name input to inject event-handler markup. The .astro dynamic-tag renderer, JSX renderer, and MDX renderer were affected, and exploitation required an application to use request-controlled or stored untrusted data as all or part of an element name. This issue is fixed in version 7.4.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Astro is a web framework for content-driven websites. Prior to 7.4.5, Astro rendered a string used as a dynamic element name as raw HTML after applying an incomplete character filter. A / in the string could make an HTML parser treat the remainder as attributes, allowing untrusted element-name input to inject event-handler markup. The .astro dynamic-tag renderer, JSX renderer, and MDX renderer were affected, and exploitation required an application to use request-controlled or stored untrusted data as all or part of an element name. This issue is fixed in version 7.4.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-126361</guid>
    </item>
    <item>
      <title>GHSA-mh32-jxcr-mh9f — Astro: XSS via attribute injection in dynamic tag names</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mh32-jxcr-mh9f</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: astro&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a dynamic tag (`const Tag = ...; &amp;lt;Tag /&amp;gt;`) resolves to a string, Astro renders it as a raw HTML element name. The name was filtered to remove characters that could inject attributes, but the filter did not handle `/`. Because HTML parsers treat `/` inside a tag as an attribute separator, a tag name such as `img/src/onerror=alert(1)` was rendered as an `&amp;lt;img&amp;gt;` element with an `onerror` attribute. The JSX renderer used for MDX did not filter string tag names at all.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```astro
---
const Tag = Astro.url.searchParams.get(&amp;#39;as&amp;#39;) ?? &amp;#39;div&amp;#39;;
---
&amp;lt;Tag&amp;gt;hello&amp;lt;/Tag&amp;gt;
```&lt;/p&gt;
&lt;p&gt;rendered `?as=img/src/onerror=alert(1)` as live HTML.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Reflected or stored cross-site scripting, but only in applications that use untrusted input (such as a request parameter or an uncontrolled CMS field) as all or part of an element name. Astro itself never derives element names from request data.&lt;/p&gt;
&lt;p&gt;Applications that let content choose an element should map that input to a fixed set of known tags. Letting untrusted input choose an element name is unsafe even with a correct filter, because it can still select elements such as `script` or `iframe`.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;`astro` &amp;lt;= 7.4.4.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `astro` 7.4.5. String tag names in `.astro` dynamic tags, JSX, and MDX now render only the leading valid element name, so characters such as `/` or `=` can no longer change the generated markup. Strings that do not start with a valid element name now throw an error.&lt;/p&gt;
&lt;p&gt;## Worka…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: astro&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;When a dynamic tag (`const Tag = ...; &amp;lt;Tag /&amp;gt;`) resolves to a string, Astro renders it as a raw HTML element name. The name was filtered to remove characters that could inject attributes, but the filter did not handle `/`. Because HTML parsers treat `/` inside a tag as an attribute separator, a tag name such as `img/src/onerror=alert(1)` was rendered as an `&amp;lt;img&amp;gt;` element with an `onerror` attribute. The JSX renderer used for MDX did not filter string tag names at all.&lt;/p&gt;
&lt;p&gt;For example:&lt;/p&gt;
&lt;p&gt;```astro
---
const Tag = Astro.url.searchParams.get(&amp;#39;as&amp;#39;) ?? &amp;#39;div&amp;#39;;
---
&amp;lt;Tag&amp;gt;hello&amp;lt;/Tag&amp;gt;
```&lt;/p&gt;
&lt;p&gt;rendered `?as=img/src/onerror=alert(1)` as live HTML.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Reflected or stored cross-site scripting, but only in applications that use untrusted input (such as a request parameter or an uncontrolled CMS field) as all or part of an element name. Astro itself never derives element names from request data.&lt;/p&gt;
&lt;p&gt;Applications that let content choose an element should map that input to a fixed set of known tags. Letting untrusted input choose an element name is unsafe even with a correct filter, because it can still select elements such as `script` or `iframe`.&lt;/p&gt;
&lt;p&gt;## Affected versions&lt;/p&gt;
&lt;p&gt;`astro` &amp;lt;= 7.4.4.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Fixed in `astro` 7.4.5. String tag names in `.astro` dynamic tags, JSX, and MDX now render only the leading valid element name, so characters such as `/` or `=` can no longer change the generated markup. Strings that do not start with a valid element name now throw an error.&lt;/p&gt;
&lt;p&gt;## Worka…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mh32-jxcr-mh9f</guid>
    </item>
  </channel>
</rss>
