<?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-06T22:24:00.110531+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-250210</id>
    <title>EUVD-2026-250210</title>
    <updated>2026-10-06T22:24:00.161462+00:00</updated>
    <content>EUVD-2026-250210</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-250210"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-55303</id>
    <title>fkie_cve-2025-55303</title>
    <updated>2026-10-06T22:24:00.161500+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Astro is a web framework for content-driven websites. In versions of astro before 5.13.2 and 4.16.18, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served. On-demand rendered sites built with Astro include an /_image endpoint which returns optimized versions of images. A bug in impacted versions of astro allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. /_image?href=//example.com/image.png. This vulnerability is fixed in 5.13.2 and 4.16.18.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-55303"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xf8x-j4p2-f749</id>
    <title>GHSA-xf8x-j4p2-f749 — Astro allows unauthorized third-party images in _image endpoint</title>
    <updated>2026-10-06T22:24:00.161534+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: astro, npm: @astrojs/node</p>
<p>### Summary</p>
<p>In affected versions of `astro`, the image optimization endpoint in projects deployed with on-demand rendering allows images from unauthorized third-party domains to be served.</p>
<p>### Details</p>
<p>On-demand rendered sites built with Astro include an `/_image` endpoint which returns optimized versions of images.</p>
<p>The `/_image` endpoint is restricted to processing local images bundled with the site and also supports remote images from domains the site developer has manually authorized (using the [`image.domains`](https://docs.astro.build/en/reference/configuration-reference/#imagedomains) or [`image.remotePatterns`](https://docs.astro.build/en/reference/configuration-reference/#imageremotepatterns) options).</p>
<p>However, a bug in impacted versions of `astro` allows an attacker to bypass the third-party domain restrictions by using a protocol-relative URL as the image source, e.g. `/_image?href=//example.com/image.png`.</p>
<p>### Proof of Concept</p>
<p>1. Create a new minimal Astro project (`astro@5.13.0`).</p>
<p>2. Configure it to use the Node adapter (`@astrojs/node@9.1.0` — newer versions are not impacted):</p>
<p>```js
   // astro.config.mjs
   import { defineConfig } from 'astro/config';
   import node from '@astrojs/node';</p>
<p>export default defineConfig({
   	adapter: node({ mode: 'standalone' }),
   });
   ```</p>
<p>3. Build the site by running `astro build`.</p>
<p>4. Run the server, e.g. with `astro preview`.</p>
<p>5. Append `/_image?href=//placehold.co/600x400` to the preview URL, e.g. &lt;http://lo…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xf8x-j4p2-f749"/>
  </entry>
</feed>
