Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · 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 · score source

EPSS

• CVE-2026-94485: 0.17% estimated exploitation activity in the next 30 days; percentile 6.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In Next.js App Router applications built with webpack, metadata image routes such as opengraph-image and twitter-image ignore the dynamicParams route segment option. An attacker can request metadata image URLs for dynamic segments that were deliberately excluded from generateStaticParams().

Published by the source

7 Oct 2026, 20:31 UTC

Last modified by the source

7 Oct 2026, 20:45 UTC

Source last checked

26 Oct 2026, 13:07 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-f87g-xv8r-7p7x

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-f87g-xv8r-7p7x

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-f87g-xv8r-7p7x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-94485

Advisory: Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass
IDs: CVE-2026-94485, GHSA-f87g-xv8r-7p7x
Record: https://patchnext.com/advisories/cve-2026-94485 (revision 4, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: next 16.3.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm next: affected >= 16.0.0, < 16.3.8; fixed in 16.3.8

## Suggested inspection (read-only)
- `npm ls next --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on next.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f87g-xv8r-7p7x (GitHub-reviewed advisory GHSA-f87g-xv8r-7p7x lists affected ranges: npm next >=16.0.0 <16.3.8)
- Verified: https://osv.dev/vulnerability/GHSA-f87g-xv8r-7p7x (OSV record GHSA-f87g-xv8r-7p7x lists affected ranges: npm next >=16.0.0 <16.3.8 (fixed))

Commands are suggestions: review each one before running it.