Tested on npm, pnpm and Yarn 4 lockfiles and a standalone Docker image

Next.js security release, November 2026: is my app patched? (16.4.5, 15.5.29)

Last checked 17 November 2026. The Next.js team published the November release on 3 November 2026. Patched versions: 16.4.5 on the 16 line and 15.5.29 on the 15 line. The release covers seven issues. Each advisory names the setup an app needs to be exposed; the table below lists them.

Which version to move to

Your lineVersion to move toSupport status
16.x16.4.5Active LTS
15.x15.5.29Maintenance LTS. Security releases for 15 continue through 31 January 2027
14.x and olderThe release post and the advisories name no patched versionListed under "Unsupported Versions" on the Next.js support policy page

The advisories name 16.4.5 as the first patched version for every 16.x release they cover, and 15.5.29 for 15.x. None of them lists a patched version on 16.0 to 16.3 or on 15.0 to 15.4, so the move is to 16.4.5 or 15.5.29. The post gives this command:

npm install next@16.4.5
npm install next@15.5.29

16.4.6 was published on 9 November 2026 and is the latest tag on npm as of 17 November. Its release notes list bug fixes and do not mention security. Every November advisory's affected range ends at 16.4.4, so 16.4.6 is outside all of them.

Does it affect my app?

Each row gives the setup in the words of the release post and the advisory. Where a source says what an issue did not affect, that sentence is quoted. A setup a row does not name is one the source does not discuss.

AdvisoryAffected versionsYou are exposed only if (from the advisory and the post)
GHSA-mfr8-8qww-v76h (High in the post, Medium on GitHub)16.3.0 to 16.4.4Cache Components is enabled, the same public use cache function is called both directly and from inside unstable_cache, and the cached function reads a root parameter, such as a tenant identifier.
GHSA-vc7v-qv4w-wrv8 (Medium)16.2.0 to 16.4.4Cache Components with nested public use cache functions, where an inner cached function reads a root parameter and returns an early value alongside a slower asynchronous value, while the outer function finishes without waiting for the slower value.
GHSA-rhh4-g77r-r9qj (Medium)16.0.0 to 16.4.4The app passes security-significant binary arguments through use cache and shares the resulting entries across callers. "It does not permit arbitrary access to unrelated cache entries."
GHSA-vvgp-ww4w-46vf (Medium)16.4.0 to 16.4.4Self-hosted with next start, Cache Components enabled, Partial Prefetching disabled or unset, and a route with a prerenderable dynamic parameter requested with a value not generated at build time, at least two deeper parameters that are never prerendered, a layout that reads the shallower of those parameters inside a Suspense boundary, and a blocking fallback shell. "Build-generated values and configurations with Partial Prefetching enabled were not affected in the reported tests." The advisory's workaround: set partialPrefetching: true in next.config.
GHSA-pc58-hwjq-p385 (Medium)16.0.0 to 16.4.4, and 15.5.28 and earlier (the advisory gives no lower bound)Self-hosted (the advisory names App Router route handlers and the fetch cache), the app returns an attacker-controlled fetched Response unchanged, behind an HTTP/1.1 reverse proxy that queues pipelined requests on a shared backend connection. "It does not apply to every reverse-proxy configuration."
GHSA-f3mh-rxg3-f5g2 (Medium)16.0.0 to 16.4.4, and 15.0.0 to 15.5.28App Router Edge Route Handlers or Pages Router Edge API routes that set cookies with NextResponse.cookies.set(), a sensitive cookie on an affected response, and attacker-controlled JavaScript on the same origin. "The reproduced leak did not affect Node.js Route Handlers or routes setting cookies through cookies().set()."
GHSA-7qx7-33qx-rqx2 (Medium)16.0.0 to 16.4.4, and 15.0.0 to 15.5.28SVG is turned off with images.dangerouslyAllowSVG: false (the default), the image source is permitted, and the image optimization backend is a native one capable of decoding SVG. The bypass works by an image being misclassified as AVIF. "The image-source allowlist still applies."

The release post lists the "shared shell cache poisoning in self-hosted applications" item without an advisory link. GitHub has an advisory published the same day, GHSA-vvgp-ww4w-46vf, whose title describes cache poisoning of shared fallback shells and whose preconditions match the post's text. We matched the two by that description. The post does not name the id.

GHSA-pc58-hwjq-p385 gives its 15.x affected range as "<= 15.5.28", with no lower bound, and 15.5.29 as the patched version. It names no patched version for 14.x or older. The other six advisories' ranges start at 15.0.0 or later.

The release announcement said seven medium issues. The post then labels GHSA-mfr8-8qww-v76h High, and the GitHub advisory record for it says Medium. npm audit and pnpm audit reported it as moderate on 17 November (below).

What your alert says

Run against a test project's lockfile with next 16.4.4, on 17 November 2026, npm audit (npm 11.19.1) printed the lines below. The last two lines depend on the version range in your package.json: where the range allows 16.4.6, npm prints fix available via `npm audit fix` instead.

next  16.2.0 - 16.4.4
Severity: moderate
Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache() - https://github.com/advisories/GHSA-mfr8-8qww-v76h
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata - https://github.com/advisories/GHSA-vc7v-qv4w-wrv8
fix available via `npm audit fix --force`
Will install next@16.4.6, which is outside the stated dependency range

pnpm audit (pnpm 10) printed the same two advisories, each as "moderate", with "Patched versions >=16.4.5", and ended with "2 vulnerabilities found". Yarn 4 yarn npm audit listed the same two. All three managers reported two of the seven advisories on that day. The other five (GHSA-rhh4-g77r-r9qj, GHSA-pc58-hwjq-p385, GHSA-vvgp-ww4w-46vf, GHSA-f3mh-rxg3-f5g2, GHSA-7qx7-33qx-rqx2) did not appear, so a clean audit on 16.4.4 is not evidence that the other five do not apply. After moving to 16.4.5, npm audit printed "found 0 vulnerabilities" and pnpm audit printed "No known vulnerabilities found". On the same day, GitHub's global advisory database returned records for those two ids only; all seven are published on the Next.js repository's security advisories page.

Check your lockfile

Run this in the repository root. It reads package-lock.json, pnpm-lock.yaml and yarn.lock (Yarn 1 and Yarn Berry), in every folder below the root, including next installed under another name (npm:next@…), and prints each version against the patched version for its line. It does not read Bun lockfiles or npm lockfileVersion 1, and says so for each such file it finds. If it prints "no next found in this file" for a lockfile in a project that uses next, it could not read that file: check that file by hand.

d=$(mktemp -d); n=0; bad=0; c=0
find . -name node_modules -prune -o \( -name package-lock.json -o -name pnpm-lock.yaml -o -name yarn.lock -o -name 'bun.lock*' \) -print > "$d/f"
while read -r f; do
  case $f in *bun.lock*) echo "$f NOT READ: this script does not read Bun lockfiles"; continue;; esac
  if grep -q '"lockfileVersion": 1,' "$f"; then echo "$f NOT READ: npm lockfileVersion 1"; continue; fi
  awk '/node_modules\/next"/||/^ +"name": "next",?$/||/^"?next@/||/^"[^"]*@npm:next@/{g=1;next} g&&/^ +"?version"?[: ]/{gsub(/[",:]/,"");print $2;g=0} /^ +[\x27\/]*next@[0-9]/{s=$1;sub(/.*next@/,"",s);sub(/[(:\x27].*/,"",s);print s}' "$f" | sort -u > "$d/v"
  [ -s "$d/v" ] || echo "$f no next found in this file"
  while read -r v; do
    case $v in *-*) p=pre;; 16.*) p=16.4.5;; 15.*) p=15.5.29;; *) p=;; esac
    if [ "$p" = pre ]; then r="pre-release, not compared: read the advisory ranges"; c=$((c+1))
    elif [ -z "$p" ]; then r="no patched version for this line in the November 2026 post or advisories"
    elif [ "$(printf '%s\n%s\n' "$p" "$v" | sort -V | head -1)" = "$p" ]; then r="ok (>= $p)"
    else r="OLDER than $p"; bad=$((bad+1)); fi
    echo "$f next@$v $r"; n=$((n+1))
  done < "$d/v"
done < "$d/f"
echo "$n next version(s) found, $bad older than the patched version, $c pre-release not compared"
[ "$n" -gt 0 ] || echo "No next found. This is not a pass: run it in the repository root and read any NOT READ line above."
rm -rf "$d"

Tested on 17 November 2026 on Debian with bash 5.2, GNU sort and mawk, against lockfiles from public projects (npm lockfileVersion 3; pnpm lockfile 6.0 and 9.0; Yarn 1; Yarn Berry, including monorepos with two and three copies of next) and against test lockfiles with next installed under another name in npm, Yarn 1 and Yarn Berry. Not run: zsh, macOS, BusyBox, Windows, npm lockfileVersion 2. A pre-release such as a canary is listed but not compared. The script reads the lockfile, so it shows what an install would give, not what is deployed.

Docker and standalone builds

A standalone or Docker build copies next into the image, so changing the lockfile does not change a running container. The image has to be rebuilt and redeployed.

To see what a given image runs:

docker run --rm IMAGE node -e "console.log(require('next/package.json').version)"

Tested on a standalone build (output: "standalone", multi-stage Dockerfile, Node 24, Next.js 16.4.4 then 16.4.5): the image built at 16.4.4 printed 16.4.4. After the lockfile on disk was changed to 16.4.5, the same image still printed 16.4.4. After a rebuild from that lockfile, the new image printed 16.4.5. Not run: images built with other base images, Bun, or a registry pull or deploy step; the check reads the image you give it, not what your platform is serving.

Vercel

The release post does not mention a Vercel platform mitigation for these issues. Vercel's security bulletin index, read on 17 November 2026, has no Next.js entry for November.

Prepared by CyberNative AI LLC, an AI-run company, using AI agents. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.

Next step

See which dated end-of-support changes your repository touches, including Node versions in .nvmrc and Node image tags in Dockerfiles. It runs in your browser; nothing is uploaded.

For the December release, watch the Next.js blog: the team said in July that it would publish advance notice of the expected release timeline and highest anticipated severity.