CVE-2026-54300
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited@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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe @astrojs/netlify adapter incorrectly converts Astro image.remotePatterns into Netlify Image CDN regex patterns with broader matching semantics. Wildcard hostnames like *.example.com become optional subdomain patterns matching the apex, and wildcard paths like /ok/* lose end anchoring, allowing prefix matches. This makes image access restrictions more permissive than configured.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify @astrojs/netlify adapter versionRun 'npm list @astrojs/netlify' or check package.json dependencies to see the installed versionAffected if The installed version is below 7.0.13 and the adapter is in use
-
Locate Astro configuration fileFind astro.config.mjs or astro.config.ts in the project rootAffected if A configuration file exists with image.remotePatterns defined
-
Inspect remotePatterns for wildcard hostnamesOpen astro.config.mjs and examine the image.remotePatterns array for entries with hostname containing '*.example.com' style wildcardsAffected if Any remotePatterns entry uses a hostname pattern starting with '*.' (e.g., '*.example.com')
-
Inspect remotePatterns for wildcard pathsReview the path field in remotePatterns for patterns ending with '/*' (e.g., '/ok/*')Affected if Any remotePatterns entry uses a path pattern ending with '/*' without explicit end anchoring
You are affected if @astrojs/netlify version is below 7.0.13 AND your configuration uses wildcard hostnames (*.domain.com) or wildcard paths ending in /* in image.remotePatterns, as these get converted to overly permissive Netlify Image CDN patterns.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade @astrojs/netlify to version 7.0.13 or later to receive the corrected pattern conversion logic.
7.0.13
- Check the current version of @astrojs/netlify in your project (package.json or package-lock.json)
- Run npm install @astrojs/[email protected] or yarn add @astrojs/[email protected] to upgrade to the fixed version
- Verify the upgrade was successful by checking the installed version
- Test that image configurations with remotePatterns work correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54300 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data