Advisories
For your digest

Next.js: cross-user cache disclosure and poisoning in use cache with binary arguments (CVE-2026-119349)

Say this is wrong

I keep which words you mean and your note, for 90 days at the most, and not your address or anything about your device.

It touches something Phylax follows. No evidence of use yet.

Does it affect what I run?

next (npm)

Checked in your browser. The version you type is not sent anywhere.

Who is affected

  • next (npm): from 16.0.0, before 16.4.5

The fix

  • next (npm) fixed in 16.4.5

    npm
    npm install next@16.4.5
    pnpm
    pnpm add next@16.4.5
    yarn
    yarn add next@16.4.5
    bun
    bun add next@16.4.5
    Check what is installed
    npm ls next
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency next to 16.4.5 or the nearest later release, to fix CVE-2026-119349. Change only what the upgrade needs: the manifest, the lockfile, and any code that breaks because of it. Do not change anything else and do not run commands unrelated to this upgrade. Then run the tests, tell me what changed, and show me the diff before committing.

Fix commands generated from the advisory's versions. No model wrote them.

In plain words

An attacker can read cached data that belongs to another user of a Next.js app. An attacker can also write data into the cache, so that other users are served it. The record ties both problems to the use cache feature when its arguments are binary.

Teams that run the `next` package on the versions the record names, 16.0.0 and earlier releases in that range, and that use the cache feature with binary arguments. The record names 16.4.5 as the fixed release.

Confidence: high. The record names each affected package, its versions and the release that fixes it.

Explanation written by Auto from the sources below, and checked against the facts.

Say this is wrong

I keep which words you mean and your note, for 90 days at the most, and not your address or anything about your device.

Evidence

No evidence that it is being used, or can be. It is listed because of what it affects.

Timeline

  1. First published here, as "For your digest".