Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-102983

Vulnerability in @astrojs/netlify (CVE-2026-102983)

Summary

Vulnerability in @astrojs/netlify (CVE-2026-102983). Risk of unauthorized operations or information disclosure. Exploitable via images.example.com. Mitigation: upgrade to 8.2.4 or later.

Original description

The description as published by the source.

Summary

The @astrojs/netlify adapter generated regular expressions for Netlify Image CDN remote-image allowlists without anchoring them to the beginning of the URL. Netlify evaluates these expressions with RegExp.test(), so an allowed image origin appearing anywhere in a URL, including its path or query string, could satisfy the allowlist.

For example, an application allowing images.example.com could accept a source URL such as:

http://127.0.0.1:6379/?url=https://images.example.com/image.png

The allowlist matched the approved origin in the query string, but Netlify parsed and fetched the URL whose actual host was 127.0.0.1.

Impact

An unauthenticated attacker can bypass the configured image.domains or image.remotePatterns allowlist through the public /.netlify/images endpoint and cause Netlify Image CDN to make requests to attacker-selected URLs. This may allow probing or reaching internal services, depending on Netlify's network-level egress protections.

The Image CDN attempts to transform responses as images, which limits direct response exfiltration. No confidentiality or integrity impact has been demonstrated.

Affected versions

@astrojs/netlify versions from 5.2.0 through 8.2.3.

Patches

Fixed in @astrojs/netlify 8.2.4. Generated remote-image allowlist expressions are now anchored to both the beginning and end of the source URL.

Workarounds

Upgrade to @astrojs/netlify 8.2.4 or later. Before upgrading, disable Netli…

Source: NIST National Vulnerability Database 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-102983 has been found in @astrojs/netlify.
Attackers can target a specific entry point like images.example.com over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @astrojs/netlify to 8.2.4 or later.
If unsure, ask your IT team or search "@astrojs/netlify CVE-2026-102983" on the vendor's site.

CVE-2026-102983 (@astrojs/netlify) — CWE-625
Attack surface: images.example.com / image.domains / image.remotePatterns
Patched: 8.2.4 — apply immediately
Workaround: Upgrade to @astrojs/netlify 8.2.4 or later.
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

A vulnerability (CWE-625) exists in @astrojs/netlify. Attackers reach the vulnerable code path via images.example.com.

📍 Affected scope

Check the vendor advisory for the affected versions of @astrojs/netlify. Attack surface: images.example.com / image.domains / image.remotePatterns.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.2.4.

🛡️ Workaround

Workaround: Upgrade to @astrojs/netlify 8.2.4 or later.

🔍 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 temporary workaround mitigate 
    Upgrade to `@astrojs/netlify` 8.2.4 or later.

    パッチが適用されるまでの応急処置として、Upgrade to @astrojs/netlify 8.2.4 or later. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @astrojs/netlify to 8.2.4

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

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

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

Affected packages

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

References

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