# CVE-2024-51479: Authorization bypass in Next.js

> Attackers can bypass middleware-based authorization checks for root-level pages in Next.js applications, potentially accessing protected resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Dec 2024
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-7gfc-8cq8-jh5f, MINI-9vw2-5xjf-3g9f, ROOT-APP-NPM-CVE-2024-51479

## What is CVE-2024-51479?

CVE-2024-51479 is a high-severity authentication bypass vulnerability in Vercel Next.js, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2024-51479?

2 open source packages ship an affected version, including next. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 9.5.5 | 14.2.15 |
| `next` | npm | From 9.5.5 | 14.2.15 |

Products: Vercel Next.js.

## How do I fix CVE-2024-51479?

Upgrade next to 14.2.15 or later.

## Is CVE-2024-51479 being exploited?

There is no known exploitation of CVE-2024-51479 in the wild and no public exploit code.

## Other vulnerabilities in Vercel Next.js

- [CVE-2025-29927](https://insights.sbomify.com/CVE-2025-29927/): Authorization Bypass in Next.js Middleware (critical 9.1)
- [CVE-2026-44578](https://insights.sbomify.com/CVE-2026-44578/): Next.js: Server-side request forgery in applications using WebSocket upgrades (high 8.6)
- [CVE-2026-94483](https://insights.sbomify.com/CVE-2026-94483/): Next.js: Server-Side Request Forgery in Image Optimization (high 8.3)
- [CVE-2026-64642](https://insights.sbomify.com/CVE-2026-64642/): Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale (high 8.3)
- [CVE-2026-64645](https://insights.sbomify.com/CVE-2026-64645/): Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51479 and fix it if it is affected.

What it is: CVE-2024-51479 is a high-severity authentication bypass vulnerability in Vercel Next.js, published on 17 Dec 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51479 in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 9.5.5; fixed in 14.2.15
- next (npm): affected from 9.5.5; fixed in 14.2.15

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51479/ (Markdown: https://insights.sbomify.com/CVE-2024-51479/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51479
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51479
- OSV: https://osv.dev/vulnerability/CVE-2024-51479

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51479/
Summaries are generated and may contain mistakes; the official description above is the record.