vercel · Next.js · published 2026-07-27

CVE-2026-64642Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale

Routine No exploitation evidence; EPSS 0.6%.

CVE-2026-64642 is not known to be exploited in the wild. EPSS estimates a 0.6% chance of exploitation in the next 30 days, higher than 51% of all CVEs. This Next.js vulnerability: CVSS 8.3 (v4.0). Fixed upstream in Next.js 16.2.11, 15.5.21. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Next.js 16.2.11, 15.5.21.

Patch events

  1. This monthSecurity release

    Web frameworkNext.js

    Next.js security releases: 16.2.11, 15.5.21

    Upgrade to 16.2.1115.5.21

    Why: Vendor security release for server software (most severe: CVE-2026-64642).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.6% (51th pct)FIRST EPSS v2026.06.15
CVSS base score8.3 (v4.0)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

Next.js is a React framework for building full-stack web applications. In versions 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication. This issue has been fixed in version 16.2.11.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →