# CVE-2026-94483: Next.js: Server-Side Request Forgery in Image Optimization

> Attackers can exploit DNS rebinding in Next.js Image Optimization to access private network resources if remote image patterns are configured.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/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:** 2 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** CLEANSTART-2026-CR16347, CLEANSTART-2026-JD47391, CLEANSTART-2026-WN21226, ECHO-7713-e30d-2172, GHSA-cjq9-62q9-8jv4, MINI-h5wq-85mw-5xhp, MINI-wxvw-68xw-f64f, MINI-x3c9-qjj9-59j5, ROOT-APP-NPM-CVE-2026-94483

## What is CVE-2026-94483?

CVE-2026-94483 is a high-severity server-side request forgery vulnerability in Vercel Next.js, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL that matches images.remotePatterns, allowing the optimized image fetch to reach private IP addresses after the URL passes the allow-list check. Applications without images.remotePatterns are not affected. Administrators unable to upgrade should audit allow-listed hosts and avoid entries whose DNS records are not trusted. This issue is fixed in version 16.3.8.

Weakness: CWE-918 (Server-Side Request Forgery)

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

2 open source packages ship an affected version, including next. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 16.0.0 | 16.3.8 |
| `next` | npm | From 16.0.0 | 16.3.8 |

Products: Vercel Next.js.

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

Upgrade next to 16.3.8 or later.

## Is CVE-2026-94483 being exploited?

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

## Other vulnerabilities in Vercel Next.js

- [CVE-2025-29927](https://insights.sbomify.com/CVE-2025-29927/): Authorization Bypass in Next.js Middleware (critical 9.1)
- [CVE-2026-44578](https://insights.sbomify.com/CVE-2026-44578/): Next.js: Server-side request forgery in applications using WebSocket upgrades (high 8.6)
- [CVE-2026-64642](https://insights.sbomify.com/CVE-2026-64642/): Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale (high 8.3)
- [CVE-2026-64645](https://insights.sbomify.com/CVE-2026-64645/): Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (high 8.3)
- [CVE-2026-64649](https://insights.sbomify.com/CVE-2026-64649/): Next.js: Server-Side Request Forgery in Server Actions on Custom Servers (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94483 is a high-severity server-side request forgery vulnerability in Vercel Next.js, published on 2 Oct 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-94483 in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 16.0.0; fixed in 16.3.8
- next (npm): affected from 16.0.0; fixed in 16.3.8

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-94483/ (Markdown: https://insights.sbomify.com/CVE-2026-94483/index.md)
```

## Sources

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

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