What is CVE-2026-94485?

CVE-2026-94485 is Next.js: Information disclosure in Next.js App Router metadata image routes via dynamicParams bypass. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-346 CWE-346.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-94485. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-94485 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-94485 using CVSS 6.3, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumInfo Disclosurepublic exploit

CVE-2026-94485

CVE-2026-94485 — Next.js: Information disclosure in Next.js App Router metadata image routes via dynamicParams bypass

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the `next dev` development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

Published Oct 2, 2026Updated Oct 2, 2026Sources: NVD, vercel (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

vercel

next.js

CVSS base

6.3

medium

Remediation

The vendor's own words where we have them.

Upgrade next.js to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
vercel	next.js	>= 16.0.0, < 16.3.8	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Scope

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.3	CVSS 4.0	medium	—	—	vercel (CNA)

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-346 · Origin Validation Error

Gain Privileges or Assume Identity
Varies by Context

Weakness & attack patterns

CWE-346

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-111 · JSON Hijacking (aka JavaScript Hijacking)CAPEC-141 · Cache PoisoningCAPEC-142 · DNS Cache PoisoningCAPEC-160 · Exploit Script-Based APIsCAPEC-21 · Exploitation of Trusted IdentifiersCAPEC-384 · Application API Message Manipulation via Man-in-the-MiddleCAPEC-385 · Transaction or Event Tampering via Application API ManipulationCAPEC-386 · Application API Navigation RemappingCAPEC-387 · Navigation Remapping To Propagate Malicious ContentCAPEC-388 · Application API Button HijackingCAPEC-510 · SaaS User Request ForgeryCAPEC-59 · Session Credential Falsification through Prediction

T1557.002Adversary-in-the-Middle: ARP Cache Poisoning
T1584.002Compromise Infrastructure: DNS Server
T1134Access Token Manipulation

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable next.js.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.3 (AV:N)
Oct 2, 2026 · NVD
Initial · CVE published
Oct 2, 2026 · NVD
CVE published by MITRE.
Oct 2, 2026 · SOCRadar CTI

References

3 on the record

github.com/vercel/next.js/commit/2d9f50a409312696145b82b3157aadb6b1fef476
Exploit, Third Party Advisory, Mitre, NIST
github.com/vercel/next.js/releases/tag/v16.3.8
Exploit, Third Party Advisory, Mitre, NIST
github.com/vercel/next.js/security/advisories/GHSA-f87g-xv8r-7p7x
Exploit, Third Party Advisory, Mitre, NIST

Elsewhere on this site

vercelevery CVE for this vendor
Info Disclosuresame class
CWE-346other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-94485 is Next.js: Information disclosure in Next.js App Router metadata image routes via dynamicParams bypass, a medium vulnerability affecting next.js from vercel. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-94485. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.3 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.