Categories
CVE-2026-54300 medium CVSS 5.3

SSRF (Server-Side Request Forgery) in @astrojs/netlify (CVE-2026-54300)

Summary

SSRF in @astrojs/netlify (CVE-2026-54300). Risk of unauthorized operations or information disclosure. Exploitable via image.remotePatterns. Mitigation: upgrade to 7.0.13 or later.

Original description

The description as published by the source.

@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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54300 has been found in @astrojs/netlify.
Attackers can target a specific entry point like image.remotePatterns over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade @astrojs/netlify to 7.0.13 or later.
If unsure, ask your IT team or search "@astrojs/netlify CVE-2026-54300" on the vendor's site.

CVE-2026-54300 (@astrojs/netlify) — CWE-918 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: image.remotePatterns / images.remote_images / localhost / matchHostname
Patched: 7.0.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

SSRF (CWE-918) exists in @astrojs/netlify. Attackers reach the vulnerable code path via image.remotePatterns without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of @astrojs/netlify. Attack surface: image.remotePatterns / images.remote_images / localhost / matchHostname.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 7.0.13.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@astrojs/netlify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r '@astrojs/netlify' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @astrojs/netlify を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade @astrojs/netlify to 7.0.13

    ステージング環境で 7.0.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @astrojs/netlify
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.0.13"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details