# CVE-2024-47831: Next.js image optimization has Denial of Service condition

> Attackers can cause excessive CPU consumption leading to Denial of Service in Next.js image optimization, affecting standard configurations.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2024
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-g77x-44xx-532m, MINI-xgjh-vx4f-288g, ROOT-APP-NPM-CVE-2024-47831

## What is CVE-2024-47831?

CVE-2024-47831 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 14 Oct 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 the Web. Cersions on the 10.x, 11.x, 12.x, 13.x, and 14.x branches before version 14.2.7 contain a vulnerability in the image optimization feature which allows for a potential Denial of Service (DoS) condition which could lead to excessive CPU consumption. Neither the `next.config.js` file that is configured with `images.unoptimized` set to `true` or `images.loader` set to a non-default value nor the Next.js application that is hosted on Vercel are affected. This issue was fully patched in Next.js `14.2.7`. As a workaround, ensure that the `next.config.js` file has either `images.unoptimized`, `images.loader` or `images.loaderFile` assigned.

Weakness: CWE-674 (Uncontrolled Recursion)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 10.0.0 | 14.2.7 |
| `next` | npm | From 10.0.0 | 14.2.7 |

Products: Vercel Next.js.

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

Upgrade next to 14.2.7 or later.

## Is CVE-2024-47831 being exploited?

There is no known exploitation of CVE-2024-47831 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-47831 and fix it if it is affected.

What it is: CVE-2024-47831 is a medium-severity denial of service vulnerability in Vercel Next.js, published on 14 Oct 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-47831 in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 10.0.0; fixed in 14.2.7
- next (npm): affected from 10.0.0; fixed in 14.2.7

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-47831/ (Markdown: https://insights.sbomify.com/CVE-2024-47831/index.md)
```

## Sources

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

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