CVE-2026-54300
Received Received - Intake
Remote URL Pattern Bypass in Astro Netlify Adapter

Publication date: 2026-06-22

Last updated on: 2026-06-22

Assigner: GitHub, Inc.

Description
@astrojs/netlify is an adapter that allows Astro to deploy your hybrid or server rendered site to Netlify. Prior to 7.0.13, @astrojs/netlify converts Astro image.remotePatterns into Netlify Image CDN images.remote_images regular expressions with broader semantics than Astro's canonical matcher. A single wildcard hostname such as *.example.com is converted to an optional subdomain regex, so the apex host matches. A single wildcard pathname such as /ok/* is converted without end anchoring, so deeper paths match by prefix. This vulnerability is fixed in 7.0.13.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-22
Last Modified
2026-06-22
Generated
2026-06-23
AI Q&A
2026-06-22
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
astrojs netlify to 7.0.13 (exc)
astrojs netlify From 7.0.13 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The CVE-2026-54300 vulnerability affects the @astrojs/netlify package versions 7.0.10 and below. It occurs because the package converts Astro's image.remotePatterns into Netlify Image CDN regex patterns with broader semantics than intended.

Specifically, wildcard hostnames like *.example.com are converted to regex patterns that also allow the apex host (example.com) to match, and wildcard pathnames like /ok/* are converted without end anchoring, permitting deeper paths to match by prefix.

This mismatch means that the Netlify Image CDN may accept URLs that Astro's own matcher would reject, potentially exposing unintended image resources.

For example, a request to /ok/a/b.svg would be allowed by Netlify's CDN even though Astro's helper would reject it.

The vulnerability is classified as CWE-918 (Server-Side Request Forgery) because the CDN may fetch URLs from unintended sources.

This issue is fixed in @astrojs/netlify version 7.0.13 and later.

Impact Analysis

This vulnerability can impact you by allowing the Netlify Image CDN to accept and fetch image URLs that were not intended to be accessible according to Astro's original matching rules.

As a result, unauthorized access to restricted or sensitive image resources may occur, potentially leading to confidentiality breaches.

The CVSS score of 5.3 indicates a moderate severity primarily due to this potential confidentiality impact.

Compliance Impact

The vulnerability in @astrojs/netlify allows broader matching of image URLs than intended, potentially exposing restricted image resources to unauthorized access. This could lead to confidentiality breaches of sensitive data.

Such unauthorized exposure of confidential information may impact compliance with data protection standards and regulations like GDPR and HIPAA, which require strict controls over access to sensitive data.

However, the provided information does not explicitly discuss compliance implications or specific regulatory impacts.

Detection Guidance

This vulnerability involves the @astrojs/netlify package versions 7.0.10 and below converting Astro's image.remotePatterns into broader regex patterns that allow unintended URL matches. Detection involves identifying if your system uses a vulnerable version of @astrojs/netlify and checking if the Netlify Image CDN is accepting image URLs that should be rejected by Astro's canonical matcher.

You can detect the vulnerability by verifying the installed package version with a command like:

  • npm list @astrojs/netlify

To check if the Netlify Image CDN is accepting unintended URLs, you can attempt to request image URLs that exploit the broader regex matching, such as accessing deeper paths beyond the intended pattern (e.g., /ok/a/b.svg) and observe if they are served.

Network monitoring tools or logs can be inspected for requests to image URLs that should be rejected by Astro's matcher but are accepted by the CDN.

Mitigation Strategies

The primary mitigation step is to update the @astrojs/netlify package to version 7.0.13 or later, where the vulnerability is fixed by aligning the regex generation with Astro's canonical matching semantics.

Until the update is applied, review and restrict image.remotePatterns configurations to avoid broad wildcard patterns that could be exploited.

Monitor your Netlify Image CDN logs for unexpected image requests that might indicate exploitation attempts.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54300. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart