Astro
Astro has Full-Read SSRF in error rendering via Host: header injection
Astro is a web framework. Prior to version 9.5.4, Server-Side Rendered pages that return an error with a prerendered custom error page (eg. `404.astro` or `500.astro`) are vulnerable to SSRF. If the `Host:` header is changed to an attacker's server, it will be fetched on `/500.html` and they can redirect this to any internal URL to read the response body through the first request. An attacker who can access the application without `Host:` header validation (eg. through finding the origin IP behind a proxy, or just by default) can fetch their own server to redirect to any internal IP. With this they can fetch cloud metadata IPs and interact with services in the internal network or localhost. For this to be vulnerable, a common feature needs to be used, with direct access to the server (no proxies). Version 9.5.4 fixes the issue.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 9.5.4
Fixed in 9.5.4
Mitigation
Upgrade astro to 9.5.4 or later.
References
- Vendor advisory github.com/withastro/astro/security/advisories…
- Patch github.com/withastro/astro/commit/e01e98b063e9…
- Release notes github.com/withastro/astro/releases/tag/%40ast…
Timeline
Days relative to CVE publicationFirst public PoC 72 days after publication; not in CISA KEV. First PoC: nuclei template: Astro SSR - Server-Side Request Forgery (nuclei template, 6 May 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Astro SSR - Server-Side Request Forgery | 6 May 2026 | 16 Nov 2026 |