# CVE-2026-33768: Astro: Unauthenticated Path Override via `x-astro-path` / `x_astro_path`

> Attackers can bypass Vercel path restrictions and access protected endpoints by manipulating headers or query parameters in unauthenticated requests.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-mr6q-rp88-fx84

## What is CVE-2026-33768?

CVE-2026-33768 is a medium-severity missing authorization vulnerability in withastro astro, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Astro is a web framework. Prior to version 10.0.2, the @astrojs/vercel serverless entrypoint reads the x-astro-path header and x_astro_path query parameter to rewrite the internal request path, with no authentication whatsoever. On deployments without Edge Middleware, this lets anyone bypass Vercel's platform-level path restrictions entirely. The override preserves the original HTTP method and body, so this isn't limited to GET. POST, PUT, DELETE all land on the rewritten path. A Firewall rule blocking /admin/* does nothing when the request comes in as POST /api/health?x_astro_path=/admin/delete-user. This issue has been patched in version 10.0.2.

Weakness: CWE-862 (Missing Authorization), CWE-441 (Unintended Proxy or Intermediary)

## Which versions are affected by CVE-2026-33768?

2 open source packages ship an affected version, including @astrojs/vercel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@astrojs/vercel` | npm | All versions | 10.0.2 |
| `@astrojs/vercel` | npm | All versions | 10.0.2 |

Products: Astro \@Astrojs\/Vercel.

## How do I fix CVE-2026-33768?

Upgrade @astrojs/vercel to 10.0.2 or later.

## Is CVE-2026-33768 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33768 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33768 and fix it if it is affected.

What it is: CVE-2026-33768 is a medium-severity missing authorization vulnerability in withastro astro, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33768 exists.

Affected packages and fixed versions:
- @astrojs/vercel (npm): affected all versions; fixed in 10.0.2
- @astrojs/vercel (npm): affected all versions; fixed in 10.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33768/ (Markdown: https://insights.sbomify.com/CVE-2026-33768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33768
- OSV: https://osv.dev/vulnerability/CVE-2026-33768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33768/
Summaries are generated and may contain mistakes; the official description above is the record.