CVE-2025-58179

CVE-2025-58179 is a high-severity server-side request forgery (SSRF) vulnerability in @astrojs/cloudflare (npm), affecting versions >= 11.0.3, < 12.6.6. It is fixed in 12.6.6.

Summary

When using Astro's Cloudflare adapter (@astrojs/cloudflare) configured with output: 'server' while using the default imageService: 'compile', the generated image optimization endpoint doesn't check the URLs it receives, allowing content from unauthorized third-party domains to be served.

Details

On-demand rendered sites built with Astro include an /_image endpoint, which returns optimized versions of images.

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 or image.remotePatterns options).

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.

PoC

  1. Create a new minimal Astro project ([email protected])

  2. Configure it to use the Cloudflare adapter (@astrojs/[email protected]) and server output:

    // astro.config.mjs
    import { defineConfig } from 'astro/config';
    import cloudflare from '@astrojs/cloudflare';
    
    export default defineConfig({
      output: 'server',
      adapter: cloudflare(),
    });
    
  3. Deploy to Cloudflare Pages or Workers

  4. Append /_image?href=https://placehold.co/600x400 to the deployment URL.

  5. This will serve the placeholder image from the unauthorised placehold.co domain.

Impact

Allows a non-authorized third-party to create URLs on an impacted site’s origin that serve unauthorized content. This includes the risk of server-side request forgery (SSRF) and by extension cross-site scripting (XSS) if a user follows a link to a maliciously crafted URL.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2025-58179 has a CVSS score of 7.2 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.6.6); upgrading removes the vulnerable code path.

Affected versions

@astrojs/cloudflare (>= 11.0.3, < 12.6.6)

Security releases

@astrojs/cloudflare → 12.6.6 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade @astrojs/cloudflare to 12.6.6 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-58179? CVE-2025-58179 is a high-severity server-side request forgery (SSRF) vulnerability in @astrojs/cloudflare (npm), affecting versions >= 11.0.3, < 12.6.6. It is fixed in 12.6.6. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
  2. How severe is CVE-2025-58179? CVE-2025-58179 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of @astrojs/cloudflare are affected by CVE-2025-58179? @astrojs/cloudflare (npm) versions >= 11.0.3, < 12.6.6 is affected.
  4. Is there a fix for CVE-2025-58179? Yes. CVE-2025-58179 is fixed in 12.6.6. Upgrade to this version or later.
  5. Is CVE-2025-58179 exploitable, and should I be worried? Whether CVE-2025-58179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2025-58179 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2025-58179? Upgrade @astrojs/cloudflare to 12.6.6 or later.

Other vulnerabilities in @astrojs/cloudflare

CVE-2026-41321

Stop the waste.
Protect your environment with Kodem.