vulns.co
/
GKData.io MCP and API Buy me a coffee

Astro

Astro: routing and authorization must agree on resource identity

Astro's routing and permission middleware could interpret the same path differently because base-path removal did not check for a complete path segment. The maintainer limits the resulting authorization bypass to applications with a non-root base path and pathname-based middleware protection. The finding does not apply to every Astro application.

Open the referenceMaintainer AdvisoryReviewed 2026-10-03

How to use this reference

The maintainer identifies 7.2.4 as patched, and its release notes confirm segment-aware base handling. Editorial lesson: a permission decision must bind to the same canonical resource that execution resolves. Review normalization contracts between middleware and routing, and preserve resource-level checks when public path representations change.

Before reading

  • URL path normalization and framework routing
  • Middleware authorization and canonical resource identity

Context and limits

  • CVE-2026-84376. matthewp published the advisory; Ryoga-exe is credited as reporter. The affected range is astro through 7.2.3.
  • The software release page displays August 19 without a year in retrieved text. A full patch-release date is therefore not asserted; it is distinct from advisory publication and resource-edition chronology.
  • No production compromise or individual bounty is established. Learning prerequisites and generalized review guidance are editorial.

Sources

  1. Authorization bypass from missing path-segment boundary check when stripping the configured baseAstro · reviewed 2026-10-03
  2. astro@7.2.4 releaseAstro · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software