Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-94483 – SSRF – Next.js 16.0.0–16.3.7 (Image Optimization)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-94483 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Image Optimization feature of Next.js. An attacker who controls DNS resolution for a remote hostname that matches an application’s configured images.remotePatterns allow-list can cause the image-optimization fetch to resolve to a private IP address, allowing the server to reach internal network resources on the attacker’s behalf. The issue carries a CVSS v4.0 base score of 8.3 (High) and affects self-hosted Next.js deployments that configure images.remotePatterns.

Technical details

  • Root cause: Next.js’s Image Optimization allow-list validates a remote image URL’s hostname against images.remotePatterns, but the subsequent fetch re-resolves DNS for that hostname at request time rather than pinning the validated IP, allowing attacker-controlled DNS to redirect the fetch after the allow-list check has passed.
  • Trigger conditions: The application must have images.remotePatterns configured to allow at least one remote hostname, and the attacker must control (or compromise) DNS resolution for a hostname that matches that allow-list.
  • Attack vector: Network, no authentication or user interaction required; attack complexity is rated high and requires attacker-controlled attributes (e.g., control of the target domain’s DNS).
  • Impact: The optimized-image fetch can be redirected to private IP ranges, enabling SSRF against internal network services reachable from the Next.js server.
  • Applications that do not configure images.remotePatterns are not affected. Applications hosted on Vercel are not affected.

Affected software

  • Next.js versions 16.0.0 through 16.3.7 (self-hosted deployments using images.remotePatterns)
  • Fixed in Next.js 16.3.8 (Active LTS); the 15.x maintenance line is fixed in 15.5.27

Severity

  • CVSS v4.0 Base Score: 8.3 (High)
  • Vector: 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

Mitigation and recommended actions

  • Immediate: Upgrade to Next.js 16.3.8 (for the 16.x line) or 15.5.27 (for the 15.x maintenance line).
  • If no patch can be applied immediately: Audit all hostnames configured in images.remotePatterns and remove or restrict any domains whose DNS is not fully trusted or controlled; applications that do not configure images.remotePatterns are not exposed to this issue and require no action.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge