CVE-2026-64643: Next.js: Unauthenticated Disclosure of Internal Server Function endpoints

Published Jul 22, 2026
·
Updated

Impact

In 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 + Server Actions.

By itself, this disclosure is typically a recon/enumeration primitive; however, it can increase risk when combined with other weaknesses. Workarounds

Never assume any authentication claims at the use cache or use server boundary. Always authenticate within the boundary.

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
npm/next>=16.0.0<16.2.11
16.2.11
npm/next>=13.0.0<15.5.21
15.5.21
Vercel Next.js Node.js>=13.0.0<15.5.21
Vercel Next.js Node.js>=16.0.0<16.2.11

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 16.2.11
  2. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 15.5.21
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.5.21
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 16.2.11
  5. Compensating control

    Always authenticate within the boundary, and never assume any authentication claims at the use cache or use server boundary for Next.js App Router Server Actions / use cache endpoints.

Event History

Jul 22, 2026
Advisory Published
via GitHub·11:00 PM
Data Sourced
via GitHub·11:00 PM
DescriptionWeaknessAffected Software
Jul 27, 2026
CVE Published
via MITRE·05:48 PM
Data Sourced
via MITRE·05:48 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-64643?

CVE-2026-64643 has a risk rating of 37, indicating a significant vulnerability.

2

How do I fix CVE-2026-64643?

To mitigate CVE-2026-64643, ensure proper authentication checks are implemented for Server Actions and cache endpoints.

3

What types of applications are affected by CVE-2026-64643?

CVE-2026-64643 affects Next.js applications that utilize the App Router, Server Actions, or use cache endpoints.

4

What happens if I don't address CVE-2026-64643?

Failing to address CVE-2026-64643 can lead to unauthorized access to sensitive Server Action IDs by unauthenticated users.

5

When was CVE-2026-64643 published?

CVE-2026-64643 was published on July 22, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203