Astro EUVD-2026-14984

Without CVSS or EPSS scores provided, risk assessment relies on the technical details and metadata available. The attack vector is network-based and requires no authentication, but exploitation requires that an attacker identifies both a trusted host in the allowlist and a sensitive path structure to bypass. The vulnerability is classified as information disclosure, limiting the impact to confidentiality rather than integrity or availability. The lack of reported active exploitation in public KEV databases and the absence of disclosed public proof-of-concept code suggest limited weaponization so far, though the straightforward nature of the bypass (testing malicious paths containing the allowlisted prefix) means that proof-of-concept development is trivial. Organizations using Astro's image optimization or remote fetching features with remotePatterns configured should prioritize patching, as the fix is available and straightforward, and the threat model (preventing unauthorized resource access on trusted hosts) is directly relevant to many web applications.

An attacker identifies that a target organization uses Astro with remotePatterns configured to allow https://cdn.example.com/public/*. The attacker crafts a request to the Astro image optimization endpoint requesting an image from https://cdn.example.com/secret-admin/public/config.json, which bypasses the intended restriction because the allowlisted prefix /public/ appears later in the path. The server-side fetcher, due to the unanchored matching logic, treats this as valid and returns the sensitive configuration file, leaking API keys or internal service endpoints to the attacker.