<?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-18T04:16:20.756336+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-405805</id>
    <title>EUVD-2026-405805</title>
    <updated>2026-11-18T04:16:20.758550+00:00</updated>
    <content>EUVD-2026-405805</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-405805"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-126363</id>
    <title>fkie_cve-2026-126363</title>
    <updated>2026-11-18T04:16:20.758580+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Astro is a web framework for content-driven websites. From 0.2.0 until 7.1.2, the @astrojs/solid-js renderer inserted a named slot into the quoted name attribute of an astro-slot wrapper without HTML escaping. A request-controlled slot name containing a quote could terminate the attribute and inject active HTML. Exploitation required a hydrated Solid component using a client:* directive and dynamic access to the attacker-chosen slot property; a component that did not render that slot emitted only escaped fallback content. This issue is fixed in version 7.1.2.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-126363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jmv2-qgxf-f995</id>
    <title>GHSA-jmv2-qgxf-f995 — Astro: Reflected XSS via unescaped slot names in @astrojs/solid-js</title>
    <updated>2026-11-18T04:16:20.758612+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @astrojs/solid-js</p>
<p>## Summary</p>
<p>The `@astrojs/solid-js` renderer wraps named slot content passed to Solid components in an `&lt;astro-slot&gt;` element, and writes the slot name into its `name` attribute without HTML escaping. A slot name containing `"` could end the attribute and inject arbitrary HTML into the page.</p>
<p>For example, a page that takes a slot name from the request:</p>
<p>```astro
---
import Tabs from '../components/Tabs.jsx';
const tab = Astro.url.searchParams.get('tab');
---
&lt;Tabs client:load active={tab}&gt;&lt;div slot={tab}&gt;…&lt;/div&gt;&lt;/Tabs&gt;
```</p>
<p>rendered with a Solid component that renders a slot by name:</p>
<p>```jsx
export default function Tabs(props) {
	return &lt;div&gt;{props[props.active]}&lt;/div&gt;;
}
```</p>
<p>would output a `tab` value such as `x"&gt;&lt;img src=x onerror=alert(1)&gt;` as live HTML.</p>
<p>## Impact</p>
<p>Reflected cross-site scripting. An attacker who gets a user to open a crafted link can run JavaScript on the site's origin, but only in applications where all of the following are true:</p>
<p>- The page passes request-controlled input (such as a query parameter) as a slot name.
- The Solid component is hydrated with a `client:*` directive. For non-hydrated components the slot wrapper is removed from the output, together with its `name` attribute.
- The Solid component renders the attacker-chosen slot, which in practice means accessing slot props by a dynamic name. Components that never render the slot only output Astro's already escaped fallback template.</p>
<p>This is the `@astrojs/solid-js` counterpart of GHSA-8hv8-5…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jmv2-qgxf-f995"/>
  </entry>
</feed>
