LiveActive security incident?Get immediate response
CVE Record

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

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Astro sites using Server Actions may be vulnerable to denial of service if they run affected versions. The issue allows an unauthenticated oversized request to consume memory and crash the server process. Business impact is availability loss, especially for public, on-demand rendered deployments in constrained containers.

Executive priority

Treat as a timely availability fix for public Astro services, not a confirmed breach issue. Prioritize internet-facing, revenue-impacting, or containerized services where repeated crashes could create sustained downtime.

Technical view

CVE-2026-27729 affects Astro 9.0.0 through 9.5.3. Server Actions automatically parse JSON or FormData request bodies and, in affected versions, buffer them in memory without a default size limit. Astro Node adapter standalone deployments are specifically described as lacking body size protection. Version 9.5.4 contains the fix.

Likely exposure

Public SSR or on-demand rendered Astro deployments using Server Actions and the Node adapter in standalone mode are the clearest exposure. Static-only sites or deployments not using Server Actions are not described as affected in the provided sources.

Exploitation context

The advisory states no authentication is required and action names may be discoverable from public HTML form attributes. The CVSS vector rates attack complexity high. No source in the bundle indicates active exploitation or CISA KEV listing.

Researcher notes

The provided sources define the vulnerability and fix but do not provide evidence of exploitation in the wild. Avoid assuming impact beyond affected Astro versions and deployment patterns. The root weakness maps to CWE-770: allocation of resources without limits or throttling.

Mitigation direction

  • Upgrade affected Astro installations to version 9.5.4 or later.
  • Prioritize public standalone Node deployments using Server Actions.
  • Review vendor advisory and release notes before applying changes.
  • If immediate upgrade is not possible, check Astro guidance for supported mitigations.

Validation and detection

  • Inventory Astro versions across applications and containers.
  • Identify applications using Server Actions.
  • Confirm whether deployments use the Node adapter in standalone mode.
  • Verify upgraded deployments report Astro 9.5.4 or later.
  • Monitor crash-restart loops or unexplained memory exhaustion in affected services.
Prepared
Confidence
high
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-770: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27729 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2026-27729Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
withastroastro>= 9.0.0, < 9.5.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-770 · source CWE mapping

Allocation of Resources Without Limits or Throttling

Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.