CVE-2026-73423

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Astro is a web framework for content-driven websites. From 7.0.0 until 7.0.6, the composable astro/hono pipeline installs security.checkOrigin only through the middleware() primitive, while actions() and pages() can dispatch to user code independently. Mounting actions() before middleware(), as in the examples/advanced-routing example and Cloudflare Hono documentation, allows cross-origin form-encoded action requests to execute before the origin check, and using pages() without middleware() drops the check for on-demand endpoints and pages. The flaw enables blind write-only cross-site request forgery using the victim's cookies against ActionHandler.handle and PagesHandler.handleWithErrorFallback when manifest.checkOrigin is enabled; the attacker can trigger a state-mutating action or endpoint handler but cannot read the cross-origin response. The default non-composable astro() pipeline is not affected. This issue is fixed in version 7.0.6.

CVSS v3
5.1
EG Score
5.1(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (4)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

[email protected]

Patch available: withastro/astro [email protected]

https://github.com/withastro/astro/releases/tag/[email protected]
github_commit Patch Available

commit 0b30b35f8643 (withastro/astro)

Patch available: withastro/astro [email protected] (contains commit 0b30b35f8643)

https://github.com/withastro/astro/commit/0b30b35f864310bee8485c952d1877e82e2b9b1a
github_pr Patch Available

Apply the origin check to Astro Actions regardless of pipeline order

Patch available: withastro/astro [email protected] (PR #17250 merged 2026-07-02)

https://github.com/withastro/astro/pull/17250
github Patch Available

composable `astro/hono` pipeline bypasses `security.checkOrigin` when `middleware()` is absent or misordered · Advisory · withastro/astro · GitHub

https://github.com/withastro/astro/security/advisories/GHSA-8mv7-9c27-98vc

Vendor Advisories for CVE-2026-73423(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
astro—7.0.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 02:48 UTCEG score recompute
  3. 2026-08-23 05:23 UTCEG score recompute
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 06:41 UTCEG score recompute
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 07:59 UTCEG score recompute
  8. 2026-08-20 22:56 UTCEPSS rescore
  9. 2026-08-20 09:17 UTCEG score recompute
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 10:34 UTCEG score recompute
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 11:51 UTCEG score recompute
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 13:09 UTCEG score recompute
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:26 UTCEG score recompute
  20. 2026-08-16 02:15 UTCEPSS rescore
  21. 2026-08-15 15:44 UTCEG score recompute
  22. 2026-08-15 01:31 UTCEPSS rescore
  23. 2026-08-14 17:01 UTCEG score recompute
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 18:19 UTCEG score recompute
Show 4 more
  1. 2026-08-13 18:12 UTCEG score recompute
  2. 2026-08-12 21:20 UTCEG score recompute
  3. 2026-08-12 20:41 UTCEG score recompute
  4. 2026-08-12 20:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-73423?
CVE-2026-73423 is a medium vulnerability published on August 12, 2026. Astro is a web framework for content-driven websites. From 7.0.0 until 7.0.6, the composable astro/hono pipeline installs security.checkOrigin only through the middleware() primitive, while actions() and pages() can dispatch to user code independently. Mounting actions() before middleware(), as in…
When was CVE-2026-73423 disclosed?
CVE-2026-73423 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73423 actively exploited?
CVE-2026-73423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.2% of all scored CVEs.
What is the CVSS score of CVE-2026-73423?
CVE-2026-73423 has a CVSS v3 base score of 5.1 (NVD).
How do I remediate CVE-2026-73423?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73423, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-73423

Explore →

Is Your Infrastructure Affected by CVE-2026-73423?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs