Astro CVE-2025-59837

Requires the Astro image optimization/proxy endpoint (the server-side /_image route) to be reachable at runtime, which means the site must run in on-demand/SSR (server) mode rather than a purely static build where no live endpoint is served. Given the fix: the affected product must be Astro versions >= 5.13.4 and < 5.13.10 - notably, installations that applied only the prior CVE-2025-58179 fix remain vulnerable because that patch's http://, https:// and // blocklist is bypassed by backslash (\\, \, %5C) prefixes in the href parameter. No authentication or user interaction is required (PR:N/UI:N). The main limiting factor is deployment mode: static-only Astro sites without the live image proxy do not expose this attack surface; XSS realization further depends on the proxied content type (e.g. a returned SVG) being rendered in a victim's browser context.

This is a moderate-severity SSRF/XSS issue that is a real but not top-tier priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, base 7.2 High) indicates a network-reachable, low-complexity, unauthenticated flaw with a scope change - consistent with SSRF where the vulnerable proxy issues requests affecting other systems, and the low C/L impact reflecting limited data exposure plus potential reflected XSS rather than full compromise. Signals conflict on urgency: a public PoC exists (demonstrated in the GHSA advisory against raw.githubusercontent.com), which raises practical exploitability, yet the EPSS score is low at 0.35% (27th percentile), indicating no observed mass-exploitation activity, and the CVE is NOT listed in CISA KEV. The exploitation status is therefore: publicly available exploit code exists, but no confirmed active exploitation. A notable caveat: this is explicitly an incomplete-fix bypass of CVE-2025-58179, so environments that only applied the earlier patch remain exposed - the recurrence pattern (forward-slash blocklist bypassed via backslashes) suggests the input-normalization surface warrants scrutiny beyond this single fix. Net assessment: patch promptly for internet-facing Astro SSR deployments that expose the image endpoint, but this is a High-CVSS issue with currently low real-world exploitation pressure rather than an emergency.

An attacker sends a crafted request to an Astro site's image proxy endpoint (e.g. /_image?href=\\attacker-controlled-host/payload.svg), using backslashes to evade the http://, https:// and // blocklist so the server still performs a fetch to the attacker-chosen URL. This enables SSRF against internal services and, by proxying an attacker-controlled SVG, potential cross-site scripting; a working PoC is published in the GitHub Security Advisory, and exploitation is low-complexity and requires no authentication per the CVSS vector.