Astro has memory exhaustion DoS due to missing request body size limit in Server Actions

Summary

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.

Timeline

1. Feb 24, 2026, 12:46 AM UTCCVE published
2. Feb 26, 2026, 2:59 PM UTCCISA SSVC assessment

   Exploitation: poc · Automatable: no · Technical impact: partial

3. Feb 26, 2026, 2:59 PM UTCRecord last updated

Affected versions

• withastro astro

  From 9.0.0 · fixed in 9.5.4

• @astrojs/nodenpm

  From 9.0.0 · fixed in 9.5.4

References 4