# CVE-2026-102983: Astro: Netlify Image CDN allowlist bypass enables SSRF

> An unauthenticated attacker can bypass image allowlists to force the Netlify Image CDN to request internal services, potentially exposing internal network details.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-4233-jc72-56c5

## What is CVE-2026-102983?

CVE-2026-102983 is a medium-severity server-side request forgery vulnerability in @astrojs astro, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Astro is a web framework for content-driven websites. From 5.2.0 until 8.2.4, the @astrojs/netlify adapter generates regular expressions for Netlify Image CDN remote-image allowlists without anchoring them to the beginning of the URL. Because Netlify evaluates these expressions with RegExp.test(), an allowed origin appearing only in a source URL's path or query can satisfy image.domains or image.remotePatterns while the URL's actual host remains attacker-controlled. An unauthenticated request to the public /.netlify/images endpoint can therefore cause the Image CDN to request attacker-selected URLs and may probe or reach internal services. Netlify egress protections may constrain reachable targets, and image transformation limits direct response exfiltration; no confidentiality or integrity impact has been demonstrated. This issue is fixed in version 8.2.4.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-625 (Permissive Regular Expression)

## Which versions are affected by CVE-2026-102983?

2 open source packages ship an affected version, including @astrojs/netlify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@astrojs/netlify` | npm | From 5.2.0 | 8.2.4 |
| `@astrojs/netlify` | npm | From 5.2.0 | 8.2.4 |

## How do I fix CVE-2026-102983?

Upgrade @astrojs/netlify to 8.2.4 or later.

## Is CVE-2026-102983 being exploited?

There is no known exploitation of CVE-2026-102983 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102983 and fix it if it is affected.

What it is: CVE-2026-102983 is a medium-severity server-side request forgery vulnerability in @astrojs astro, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102983 in the wild and no public exploit code.

Affected packages and fixed versions:
- @astrojs/netlify (npm): affected from 5.2.0; fixed in 8.2.4
- @astrojs/netlify (npm): affected from 5.2.0; fixed in 8.2.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102983/ (Markdown: https://insights.sbomify.com/CVE-2026-102983/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102983
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102983
- OSV: https://osv.dev/vulnerability/CVE-2026-102983

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102983/
Summaries are generated and may contain mistakes; the official description above is the record.