<?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>Wed, 14 Oct 2026 14:16:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252061</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252061</link>
      <description>EUVD-2026-252061</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252061</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58179</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58179</link>
      <description>&lt;p&gt;Astro is a web framework for content-driven websites. Versions 11.0.3 through 12.6.5 are vulnerable to SSRF when using Astro&amp;#39;s Cloudflare adapter. When configured with output: &amp;#39;server&amp;#39; while using the default imageService: &amp;#39;compile&amp;#39;, the generated image optimization endpoint doesn&amp;#39;t check the URLs it receives, allowing content from unauthorized third-party domains to be served. a A bug in impacted versions of the @astrojs/cloudflare adapter for deployment on Cloudflare’s infrastructure, allows an attacker to bypass the third-party domain restrictions and serve any content from the vulnerable origin. This issue is fixed in version 12.6.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Astro is a web framework for content-driven websites. Versions 11.0.3 through 12.6.5 are vulnerable to SSRF when using Astro&amp;#39;s Cloudflare adapter. When configured with output: &amp;#39;server&amp;#39; while using the default imageService: &amp;#39;compile&amp;#39;, the generated image optimization endpoint doesn&amp;#39;t check the URLs it receives, allowing content from unauthorized third-party domains to be served. a A bug in impacted versions of the @astrojs/cloudflare adapter for deployment on Cloudflare’s infrastructure, allows an attacker to bypass the third-party domain restrictions and serve any content from the vulnerable origin. This issue is fixed in version 12.6.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58179</guid>
    </item>
    <item>
      <title>GHSA-qpr4-c339-7vq8 — Server-Side Request Forgery via /_image endpoint in Astro Cloudflare adapter</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-qpr4-c339-7vq8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/cloudflare&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When using Astro&amp;#39;s Cloudflare adapter (`@astrojs/cloudflare`) configured with `output: &amp;#39;server&amp;#39;` while using the default `imageService: &amp;#39;compile&amp;#39;`, the generated image optimization endpoint doesn&amp;#39;t check the URLs it receives, allowing content from unauthorized third-party domains to be served.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;On-demand rendered sites built with Astro include an `/_image` endpoint, which returns optimized versions of images.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;However, a bug in impacted versions of the `@astrojs/cloudflare` adapter for deployment on Cloudflare’s infrastructure, allows an attacker to bypass the third-party domain restrictions and serve any content from the vulnerable origin.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create a new minimal Astro project (`astro@5.13.3`)&lt;/p&gt;
&lt;p&gt;2. Configure it to use the Cloudflare adapter (`@astrojs/cloudflare@12.6.5`) and server output:&lt;/p&gt;
&lt;p&gt;```js
   // astro.config.mjs
   import { defineConfig } from &amp;#39;astro/config&amp;#39;;
   import cloudflare from &amp;#39;@astrojs/cloudflare&amp;#39;;&lt;/p&gt;
&lt;p&gt;export default defineConfig({
     output: &amp;#39;server&amp;#39;,
     adapter: cloudflare(),
   });
   ```&lt;/p&gt;
&lt;p&gt;3. Deploy to Cloudflare Pages…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @astrojs/cloudflare&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;When using Astro&amp;#39;s Cloudflare adapter (`@astrojs/cloudflare`) configured with `output: &amp;#39;server&amp;#39;` while using the default `imageService: &amp;#39;compile&amp;#39;`, the generated image optimization endpoint doesn&amp;#39;t check the URLs it receives, allowing content from unauthorized third-party domains to be served.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;On-demand rendered sites built with Astro include an `/_image` endpoint, which returns optimized versions of images.&lt;/p&gt;
&lt;p&gt;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).&lt;/p&gt;
&lt;p&gt;However, a bug in impacted versions of the `@astrojs/cloudflare` adapter for deployment on Cloudflare’s infrastructure, allows an attacker to bypass the third-party domain restrictions and serve any content from the vulnerable origin.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;1. Create a new minimal Astro project (`astro@5.13.3`)&lt;/p&gt;
&lt;p&gt;2. Configure it to use the Cloudflare adapter (`@astrojs/cloudflare@12.6.5`) and server output:&lt;/p&gt;
&lt;p&gt;```js
   // astro.config.mjs
   import { defineConfig } from &amp;#39;astro/config&amp;#39;;
   import cloudflare from &amp;#39;@astrojs/cloudflare&amp;#39;;&lt;/p&gt;
&lt;p&gt;export default defineConfig({
     output: &amp;#39;server&amp;#39;,
     adapter: cloudflare(),
   });
   ```&lt;/p&gt;
&lt;p&gt;3. Deploy to Cloudflare Pages…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-qpr4-c339-7vq8</guid>
    </item>
  </channel>
</rss>
