Advisories
This weekExploitable · Confirmed

next: Authorization Bypass in Next.js Middleware

There is evidence it can be used, or an emergency alert, without the proof that makes it urgent.

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 13.0.0, before 13.5.9
  • next (npm): from 14.0.0, before 14.2.25
  • next (npm): from 15.0.0, before 15.2.3
  • next (npm): from 12.0.0, before 12.3.5

The fix

  • next (npm) fixed in 13.5.9

    npm
    npm install next@13.5.9
    pnpm
    pnpm add next@13.5.9
    yarn
    yarn add next@13.5.9
    bun
    bun add next@13.5.9
    Check what is installed
    npm ls next
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency next to 13.5.9 or the nearest later release, to fix CVE-2025-29927. 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.
  • next (npm) fixed in 14.2.25

    npm
    npm install next@14.2.25
    pnpm
    pnpm add next@14.2.25
    yarn
    yarn add next@14.2.25
    bun
    bun add next@14.2.25
    Check what is installed
    npm ls next
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency next to 14.2.25 or the nearest later release, to fix CVE-2025-29927. 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.
  • next (npm) fixed in 15.2.3

    npm
    npm install next@15.2.3
    pnpm
    pnpm add next@15.2.3
    yarn
    yarn add next@15.2.3
    bun
    bun add next@15.2.3
    Check what is installed
    npm ls next
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency next to 15.2.3 or the nearest later release, to fix CVE-2025-29927. 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.
  • next (npm) fixed in 12.3.5

    npm
    npm install next@12.3.5
    pnpm
    pnpm add next@12.3.5
    yarn
    yarn add next@12.3.5
    bun
    bun add next@12.3.5
    Check what is installed
    npm ls next
    Paste into Cursor, Lovable or Claude Code
    Upgrade the npm dependency next to 12.3.5 or the nearest later release, to fix CVE-2025-29927. 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

Brief pending: here are the facts and the fix. The explanation in plain words follows when it has been written and checked.

Evidence

  • Exploitable · Confirmed

    EPSS puts the chance of exploitation in the next 30 days at 99%.

    FIRST EPSSStated

Timeline

  1. First published here, as "For your digest".
  2. Level changed from "For your digest" to "This week".
  3. Evidence added: EPSS rates exploitation in the next 30 days as more likely than not. (FIRST EPSS)