<?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-11-17T15:40:23.553902+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/euvd-2026-405802</id>
    <title>EUVD-2026-405802</title>
    <updated>2026-11-17T15:40:23.556356+00:00</updated>
    <content>EUVD-2026-405802</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405802"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126361</id>
    <title>fkie_cve-2026-126361</title>
    <updated>2026-11-17T15:40:23.556395+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-126361"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-mh32-jxcr-mh9f</id>
    <title>GHSA-mh32-jxcr-mh9f — Astro: XSS via attribute injection in dynamic tag names</title>
    <updated>2026-11-17T15:40:23.556449+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: astro</p>
<p>## Summary</p>
<p>When a dynamic tag (`const Tag = ...; &lt;Tag /&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 `&lt;img&gt;` element with an `onerror` attribute. The JSX renderer used for MDX did not filter string tag names at all.</p>
<p>For example:</p>
<p>```astro
---
const Tag = Astro.url.searchParams.get('as') ?? 'div';
---
&lt;Tag&gt;hello&lt;/Tag&gt;
```</p>
<p>rendered `?as=img/src/onerror=alert(1)` as live HTML.</p>
<p>## Impact</p>
<p>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.</p>
<p>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`.</p>
<p>## Affected versions</p>
<p>`astro` &lt;= 7.4.4.</p>
<p>## Patches</p>
<p>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.</p>
<p>## Worka…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-mh32-jxcr-mh9f"/>
  </entry>
</feed>
