Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2024-51479

next.js: next: authorization bypass in Next.js

Overview

Published
17 Dec 2024
Modified
17 Jun 2026
High CVE
1 Registry packages
13 OS packages
2 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-285, CWE-863

Affected packages · 1

Packages affected by CVE-2024-51479
EcosystemPackageVulnerableFixed in
npm next >=9.5.5, <14.2.15 14.2.15

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

Red Hat 1 release · 1 package

eol 1
aspnetcore-runtime-7-0
Red Hat fixes for CVE-2024-51479
ReleasePackageFixed in
9 aspnetcore-runtime-7-0 +11 eol

minimos 1 release · 1 package

fixed 1
trigger-dev
minimos fixes for CVE-2024-51479
ReleasePackageFixed in
trigger-dev 4.5.0-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.