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, a server-side fetch with a request body may return a cached response body from a different request to the same URL but different body. Confidential data in the POST's response body would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies to fetch calls with a request that has a different init than the one passed to fetch. A safe request would be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit). This issue has been fixed in versions 15.5.21 and 16.2.11.

The Next.js Framework on the remote host is affected by multiple vulnerabilities:

  - A server-side fetch with a request body may return a cached response body from a different request to the     same URL but different body. Confidential data in the POST's response body would then leak to unauthorized     requests, though the request itself will not be deduped. This only applies to fetch calls with a request     that has a different init than the one passed to fetch. Applications using Pages Router are not     vulnerable. (CVE-2026-64648)

  - Requests targeting Next.js applications using App Router with at least one Server Action can lead to     excessive memory consumption if that Server Action uses the Edge runtime. (CVE-2026-64646)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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, a server-side fetch with a request body may return a cached response body from
    a different request to the same URL but different body. Confidential data in the POST's response body
    would then leak to unauthorized requests. Though the request itself will not be deduped. This only applies
    to fetch calls with a request that has a different init than the one passed to fetch. A safe request would
    be: fetch(new Request(init), init). An unsafe request would be: fetch(new Request(init), aDifferentInit).
    This issue has been fixed in versions 15.5.21 and 16.2.11. (CVE-2026-64648)

ID	Name	Product	Family	Type	Severity
342581	Next.js Framework 13.x < 15.5.21 / 16.x < 16.2.11 Multiple Vulnerabilities	Nessus	Misc.	Local	medium
445180	SCA: security update for next (GHSA-68g3-v927-f742)	Tenable Cloud Security	SCA Checks	Local	medium
445180	SCA: security update for next (GHSA-68g3-v927-f742)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-64648

medium

Tenable Plugins

medium

medium

medium