vercel · Next.js · published 2026-07-27
CVE-2026-64643Next.js: Unauthenticated Disclosure of Internal Server Function endpoints
Routine No exploitation evidence; EPSS 0.5%.
CVE-2026-64643 is not known to be exploited in the wild. EPSS estimates a 0.5% chance of exploitation in the next 30 days, higher than 44% of all CVEs. This Next.js vulnerability: CVSS 6.3 (v4.0), attacks can be automated. Fixed upstream in Next.js 16.2.11, 15.5.21. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Next.js 16.2.11, 15.5.21.
Patch events
Web frameworkNext.js
Next.js security releases: 16.2.11, 15.5.21
Upgrade to
16.2.1115.5.21Why: Vendor security release for server software (most severe: CVE-2026-64642).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.5% (44th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 6.3 (v4.0)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 | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- vercel next.js
>= 13.0.0, < 15.5.21(affected)>= 16.0.0, < 16.2.11(affected)
Description (from the CVE record)#
Next.js is a React framework for building full-stack web applications. In versions 12.0.0 through 15.5.20 and 16.0.0 through 16.2.10, Next.js applications using App Router, Server Actions (use server) or use cache endpoints can be disclosed bypassing any authentication on the pages where these endpoints are usually used. Server Action IDs can be disclosed to unauthenticated users via publicly served client artifacts (for example, static chunks containing action references). Affected users are applications using App Router and Server Actions. By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses. This issue has been fixed in versions 15.5.21 and 16.2.11.
Quoted from the CVE Program record.