Astro has Full-Read SSRF in error rendering via Host: header injection

Description

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.

Recommendation

Update the @astrojs/node package to the latest compatible version. Followings are version details:

• Affected version(s): < 9.5.4
• Patched version(s): 9.5.4

References

• GHSA-qq67-mvv5-fw3g
• docs.astro.build
• CVE-2026-25545
• CWE-918
• CAPEC-310
• OWASP 2021-A10
• OWASP 2021-A6

Related Issues

• Axios has Unrestricted Cloud Metadata Exfiltration via Header Injection Chain - CVE-2026-40175
• Astro: Cache Poisoning due to incorrect error handling when if-match header is malformed - CVE-2026-41322
• SillyTavern has Authentication Bypass via SSO Header Injection - CVE-2026-44649
• Payload has an SQL Injection via Query Handling - CVE-2026-34747

You might also like:

Host Header Injection and Python Tests with SmartScanner 1.11

CSRF, XXE, and 12 Other Security Acronyms Explained

How do hackers hack websites?

Tags:

npm

@astrojs/node