CVE-2026-94483 json
Next.js: Server-Side Request Forgery in Image Optimization
published last mo. modified last mo. also EUVD-2026-91671 , GHSA-cjq9-62q9-8jv4
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 26%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm next 16.3.8
- vercel next.js 16.3.8
Is CVE-2026-94483 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-94483 updated cvss 3.7
next: Next.js: Information disclosure via SSRF in Image Optimization
-
Red Hat Enterprise Linux 7 firefox, firefox 140.16.0-1.el10_2 Red Hat Enterprise Linux 8 firefox, thunderbird, firefox 140.16.0-1.el10_2, thunderbird 140.16.0-1.el10_2 Red Hat Enterprise Linux 9 firefox, firefox-x11, thunderbird, firefox 140.16.0-1.el10_2, thunderbird 140.16.0-1.el10_2 Red Hat Enterprise Linux 10 firefox 140.16.0-1.el10_2, thunderbird 140.16.0-1.el10_2 Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9affected: workaround, no fix available “Fix deferred”
-
Red Hat Trusted Artifact Signer rhtas/rekor-search-ui-rhel9affected: workaround, no fix planned “Out of support scope”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | next | >=16.0.0, <16.3.8 |
16.3.8 |
Affected products
- vercel next.js
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
-
github.com
/vercel/next.js/commit/e002ad68bd676bb0ed0c87bb22e3590304763e0b
web, patch
-
github.com
/vercel/next.js/security/advisories/GHSA-cjq9-62q9-8jv4
web, vendor-advisory, advisory
-
github.com
/vercel/next.js/releases/tag/v16.3.8
web, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-94483
advisory
-
github.com
/vercel/next.js
package
Sources
- CVE List CVE-2026-94483
- GitHub Advisory GHSA-cjq9-62q9-8jv4
- NVD CVE-2026-94483
- Maintainer advisory GHSA-cjq9-62q9-8jv4
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.