Astro Vercel Adapter CVE-2026-73424

Exploitation requires three concurrent conditions: (1) the target application uses @astrojs/vercel version 10.0.3 through 11.0.2 with isr: true explicitly set in the Astro configuration - ISR must be actively enabled for the /_isr function to be registered and publicly addressable; (2) the target route being accessed is protected exclusively by Vercel edge-level controls, either Vercel project path rules or firewall rules that deny access to the route path, or split deployments with edgeMiddleware: true where authorization logic lives in Astro edge middleware rather than in the origin route handler; and (3) the /_isr endpoint must be publicly reachable, which is the default on Vercel deployments (the attacker does not need to send the x-vercel-isr header because Vercel itself sets it on all requests to /_isr). Routes that validate authentication inside their own server-side origin handlers (checking session tokens, JWTs, or API keys within the Astro route file) are NOT bypassed, because the attacker triggers a fresh render but the route's own auth logic still executes at origin. Non-ISR deployments and deployments not on Vercel are entirely unaffected.

The CVSS 6.5 Medium score (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N) correctly captures that exploitation requires no authentication and no user interaction over the network, but the I:L component is debatable since the attacker reads, not modifies, data - the official score may be treating the authorization control bypass itself as an integrity impact. Real-world risk is tightly gated by two deployment conditions: ISR must be explicitly enabled and route authorization must rely exclusively on edge-level controls (Vercel path rules or split edgeMiddleware), meaning applications that enforce auth inside their own origin route handlers are not affected at all. For those that do match both conditions - a non-trivial subset among Vercel-hosted Astro apps - the attack is trivially automated with a single unauthenticated GET request, and even a mid-sized municipal IT team in gniezno running a Vercel-hosted Astro app with ISR-enabled admin routes should treat this as urgent if their only access control is a Vercel path rule. No CISA KEV listing exists and no public proof-of-concept has been identified, suggesting exploitation has not yet been observed at broad scale; however, the regression nature (same root cause as CVE-2026-33768, a known and previously exploited pattern) and trivial attack primitive meaningfully elevate practical priority above what the EPSS score alone might imply. CVSS signals and description are consistent - no conflicts noted.

An attacker identifies a Vercel-hosted Astro application with ISR enabled and a route such as /admin/dashboard protected exclusively by a Vercel project path rule. The attacker issues a single unauthenticated GET request - for example, curl https://target.vercel.app/_isr?x_astro_path=/admin/dashboard - and receives a fresh origin render of the protected page in the response body, since the edge evaluated access controls only against /_isr (permitted) and never against /admin/dashboard (blocked). No public proof-of-concept code has been identified, but no specialized tooling or credentials are required beyond knowledge of the target route path.