Skip to content
Fencer Vulns
high 7.5

CVE-2024-51479 json

Authorization bypass in Next.js

published 2024-12-17 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-3534 , GHSA-7gfc-8cq8-jh5f

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
4.0%
EPSS 4.0% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm next 14.2.15
  • vercel next.js 14.2.15

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-51479 updated cvss 7.5

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

  • Red Hat Enterprise Linux 9 dotnet7.0, dotnet-host, dotnet-sdk-7.0, dotnet-hostfxr-7.0, dotnet-runtime-7.0, dotnet-templates-7.0, +6 more
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat streams for Apache Kafka com.github.streamshub-console com.github.streamshub-console
    affected: workaround, no fix available
  • Red Hat Trusted Artifact Signer 1.1 rhtas 1.1.2-1744101482
    fixed: vendor fix RHSA-2025:3807
  • Red Hat Enterprise Linux 7 firefox Red Hat Enterprise Linux 8 firefox, thunderbird Red Hat Enterprise Linux 9 firefox, firefox-x11, thunderbird
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
22 mo ago

Exploit prediction

4.00% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
npm next
>=9.5.5, <14.2.15
14.2.15

Affected products

  • vercel next.js

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of vercel/next.js published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.