PatchSiren cyber security CVE debrief
CVE-2026-73423 withastro CVE debrief
CVE-2026-73423 is a medium-severity vulnerability in the Astro web framework that allows for blind write-only cross-site request forgery (CSRF) attacks. The flaw affects Astro versions 7.0.0 through 7.0.6 and enables attackers to trigger state-mutating actions or endpoint handlers using the victim's cookies, but does not allow reading of cross-origin responses. The issue is fixed in version 7.0.6.
- Vendor
- withastro
- Product
- astro
- CVSS
- MEDIUM 5.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-12
- Original CVE updated
- 2026-09-09
- Advisory published
- 2026-08-12
- Advisory updated
- 2026-09-09
Who should care
Defenders responsible for Astro-based web applications, particularly those using the composable astro/hono pipeline, should assess exposure and prioritize upgrading to version 7.0.6 or later.
Why it matters
CVE-2026-73423 is a medium-severity vulnerability in Astro that allows for blind write-only CSRF attacks. Defenders should prioritize upgrading to version 7.0.6 or later and review pipeline configuration to prevent potential data integrity issues.
- Triggering state-mutating actions or endpoint handlers using victim's cookies
- Potential for data integrity issues due to blind write-only CSRF attacks
- Need for verification of Astro version and pipeline configuration
- Possible impact on web application security posture
Technical summary
The Astro web framework's composable astro/hono pipeline has a flaw in versions 7.0.0 through 7.0.6. The security.checkOrigin middleware is not properly installed, allowing cross-origin form-encoded action requests to execute before the origin check. This enables blind write-only cross-site request forgery (CSRF) attacks using the victim's cookies against ActionHandler.handle and PagesHandler.handleWithErrorFallback.
Defensive priority
Defenders should prioritize upgrading to Astro version 7.0.6 or later, and review their usage of the composable astro/hono pipeline to ensure proper configuration of security.checkOrigin.
Recommended defensive actions
- Upgrade to Astro version 7.0.6 or later
- Review and configure security.checkOrigin in the composable astro/hono pipeline
- Monitor for suspicious activity using victim's cookies
- Perform a thorough review of the Astro-based web application's pipeline configuration
- Verify that all instances of the affected Astro versions are identified and prioritized for remediation
- Implement additional monitoring to detect potential CSRF attacks
- Review and update incident response plans to address potential data integrity issues
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. GitHub references provide additional context on the fix and affected code.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-73423 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-73423
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-73423 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-73423
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/withastro/astro/commit/0b30b35f864310bee8485c952d1877e82e2b9b1a
-
Source reference
Unverified legacy reference
URL: https://github.com/withastro/astro/pull/17250
-
Source reference
Unverified legacy reference
URL: https://github.com/withastro/astro/releases/tag/[email protected]
-
Source reference
Unverified legacy reference
URL: https://github.com/withastro/astro/security/advisories/GHSA-8mv7-9c27-98vc
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.