CVE-2024-51479

Authorization bypass in Next.js

Published Dec 17, 2024 CVSS 3.1 · 7.5 High EPSS 4.0% KEV · Not listed
Description
Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7gfc-8cq8-jh5f Next.js authorization bypass vulnerability
History
Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Weaknesses CWE-863
CPEs cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
First Time appeared Redhat
Redhat trusted Artifact Signer
CPEs cpe:/a:redhat:trusted_artifact_signer:1.1::el9
Vendors & Products Redhat
Redhat trusted Artifact Signer
Type Values Removed Values Added
Metrics threat_severity

Important

threat_severity

Moderate

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability.
Title Authorization bypass in Next.js
Weaknesses CWE-285
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Dec 17, 2024, 8:36 PM
Reserved
Oct 28, 2024, 2:20 PM
Status
Analyzed
Published
Dec 17, 2024, 7:15 PM
Modified
Jun 17, 2026, 8:05 AM
Severity
Moderate
Public date
Dec 17, 2024, 6:13 PM