CVE-2026-94483: vercel next.js · Server-Side Request Forgery (SSRF)
Affects vercel next.jsSource CVE Database V5
Not known to be exploited · CVSS 8.3 High : upgrade to 16.3.8 soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.3.8
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade vercel next.js to 16.3.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
AI-suggested
Upgrade Next.js to version 16.3.8 or later where this vulnerability is fixed. For administrators unable to upgrade immediately, audit the allow-listed hosts in images.remotePatterns and avoid entries with untrusted DNS records to reduce risk.
Description
A Server-Side Request Forgery (SSRF) vulnerability exists in Next.js versions 16.0.0 through 16.3.7 in the Image Optimization feature when using images.remotePatterns. This allows attacker-controlled DNS resolution to bypass allow-list checks and fetch images from private IP addresses. Applications not using images.remotePatterns are not affected. The issue is fixed in version 16.3.8.