Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Authorization Bypass in Next.js Middleware

CVSS 3.1 9.1 CRITICALEUVD CVSS 3.1 9.1 CVSS 3.1 · [email protected] · Secondary 9.1 CRITICALCVSS_V3 Publisher rating CRITICALFixed by next 13.5.9Fixed by next 14.2.25Fixed by next 15.2.3Fixed by next 12.3.5KEV status unknown

cve-program · CVE-2025-29927

Published

Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.

Read the publisher's advisory

euvd · EUVD-2025-7243

Published

Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.

Read the publisher's advisory

nvd · CVE-2025-29927

Published

Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.

Read the publisher's advisory

osv · GHSA-f82v-jwr5-mffw

Published

# Impact It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. # Patches * For Next.js 15.x, this issue is fixed in `15.2.3` * For Next.js 14.x, this issue is fixed in `14.2.25` * For Next.js 13.x, this issue is fixed in 13.5.9 * For Next.js 12.x, this issue is fixed in 12.3.5 * For Next.js 11.x, consult the below workaround. _Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability._ # Workaround If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the `x-middleware-subrequest` header from reaching your Next.js application. ## Credits - Allam Rachid (zhero;) - Allam Yasser (inzo_)

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-29927

Published

next.js

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "vercel",
                    "product": "next.js",
                    "versions": [
                        {
                            "version": ">= 11.1.4, < 12.3.5",
                            "status": "affected"
                        },
                        {
                            "version": ">= 14.0.0, < 14.2.25",
                            "status": "affected"
                        },
                        {
                            "version": ">= 15.0.0, < 15.2.3",
                            "status": "affected"
                        },
                        {
                            "version": ">= 13.0.0, < 13.5.9",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-7243

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 21, 2025, 2:34:49 PM

dateUpdated: Apr 8, 2025, 3:17:05 PM

2 related source bulletins · separate from aliases

WID-SEC-W-2025-0627: Vercel Next.js: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

CVE-2025-29927

NCSC-2025-0096: Kwetsbaarheid verholpen in Next.js

CVE-2025-29927

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-29927

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-285 · CWE-863

Original publisher date fields

published: 2025-03-21T15:15:42.660

lastModified: 2026-06-17T09:05:53.640

1 source CPE criteria · context only
  • cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-f82v-jwr5-mffw

Published

next

npm

SEMVER · introduced 13.0.0 → fixed 13.5.9

next

npm

SEMVER · introduced 14.0.0 → fixed 14.2.25

next

npm

SEMVER · introduced 15.0.0 → fixed 15.2.3

next

npm

SEMVER · introduced 12.0.0 → fixed 12.3.5

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 12:50 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current