CVE-2026-33769
Unanchored Path Matching in Astro Allows Unauthorized Remote Fetches
Publication date: 2026-03-24
Last updated on: 2026-03-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| astro | astro | From 2.10.10 (inc) to 5.18.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects the Astro web framework versions from 2.10.10 up to but not including 5.18.1. It involves the remotePatterns path enforcement used by server-side fetchers, such as the image optimization endpoint. The issue is that the path matching logic for wildcards (specifically /*) is unanchored, meaning that a pathname containing the allowed prefix later in the path can still match. Consequently, an attacker can exploit this to fetch paths outside the intended allowlisted prefix on an otherwise allowed host.
This flaw has been fixed in version 5.18.1 of Astro.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can fetch resources outside the intended allowlisted paths on a permitted host. This could lead to unauthorized access to sensitive or restricted data that should not be accessible through the server-side fetchers.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Astro to version 5.18.1 or later, where the issue has been patched.