# CVE-2026-33769: Astro: Remote allowlist bypass via unanchored matchPathname wildcard

> Attackers can bypass remote URL allowlists to access unintended internal paths via unanchored wildcard matching in Astro's image optimization endpoint.

- **Severity:** Low 2.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **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-g735-7g2w-hh3f

## What is CVE-2026-33769?

CVE-2026-33769 is a low-severity server-side request forgery 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. From version 2.10.10 to before version 5.18.1, this issue concerns Astro's remotePatterns path enforcement for remote URLs used by server-side fetchers such as the image optimization endpoint. The path matching logic for /* wildcards is unanchored, so a pathname that contains the allowed prefix later in the path can still match. As a result, an attacker can fetch paths outside the intended allowlisted prefix on an otherwise allowed host. This issue has been patched in version 5.18.1.

Weakness: CWE-20 (Improper Input Validation)

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

2 open source packages ship an affected version, including astro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `astro` | npm | From 2.10.10 | 5.18.1 |
| `astro` | npm | From 2.10.10 | 5.18.1 |

Products: Astro Astro.

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

Upgrade astro to 5.18.1 or later.

## Is CVE-2026-33769 being exploited?

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

## Other vulnerabilities in withastro astro

- [CVE-2024-56159](https://insights.sbomify.com/CVE-2024-56159/): Server source code is exposed to the public if sourcemaps are enabled (high 7.8)
- [CVE-2026-54299](https://insights.sbomify.com/CVE-2026-54299/): Astro: Host header SSRF in prerendered error page fetch (high 7.5)
- [CVE-2025-59837](https://insights.sbomify.com/CVE-2025-59837/): astro allows bypass of image proxy domain validation leading to SSRF and potential XSS (high 7.2)
- [CVE-2026-50146](https://insights.sbomify.com/CVE-2026-50146/): Astro: Reflected XSS via unescaped slot name (high 7.1)
- [CVE-2025-64764](https://insights.sbomify.com/CVE-2025-64764/): Astro is vulnerable to Reflected XSS via the server islands feature (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33769 is a low-severity server-side request forgery 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-33769 exists.

Affected packages and fixed versions:
- astro (npm): affected from 2.10.10; fixed in 5.18.1
- astro (npm): affected from 2.10.10; fixed in 5.18.1

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-33769/ (Markdown: https://insights.sbomify.com/CVE-2026-33769/index.md)
```

## Sources

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

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