# GHSA-9qr9-h5gf-34mp: Next.js is vulnerable to RCE in React flight protocol

> Remote attackers can execute arbitrary code via the React flight protocol in affected Next.js and React server packages.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Dec 2025

## What is GHSA-9qr9-h5gf-34mp?

GHSA-9qr9-h5gf-34mp is a code injection vulnerability in next, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability affects certain React packages<sup>1</sup> for versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 and frameworks that use the affected packages, including Next.js 15.x and 16.x using the App Router. The issue is tracked upstream as [CVE-2025-55182](https://www.cve.org/CVERecord?id=CVE-2025-55182). 

Fixed in:
React: 19.0.1, 19.1.2, 19.2.1
Next.js: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, 15.6.0-canary.58, 16.1.0-canary.12+

The vulnerability also affects experimental canary releases starting with 14.3.0-canary.77. Users on any of the 14.3 canary builds should either downgrade to a 14.x stable release or 14.3.0-canary.76.

All users of stable 15.x or 16.x Next.js versions should upgrade to a patched, stable version immediately.

<sup>1</sup> The affected React packages are:
- react-server-dom-parcel
- react-server-dom-turbopack
- react-server-dom-webpack

## Which versions are affected by GHSA-9qr9-h5gf-34mp?

14 open source packages ship an affected version, including next.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `next` | npm | From 14.3.0-canary.77 | 15.0.5 |
| `next` | npm | From 14.3.0-canary.77 | 15.0.5 |
| `next` | npm | From 15.1.0-canary.0 | 15.1.9 |
| `next` | npm | From 15.1.0-canary.0 | 15.1.9 |
| `next` | npm | From 15.2.0-canary.0 | 15.2.6 |
| `next` | npm | From 15.2.0-canary.0 | 15.2.6 |
| `next` | npm | From 15.3.0-canary.0 | 15.3.6 |
| `next` | npm | From 15.3.0-canary.0 | 15.3.6 |
| `next` | npm | From 15.4.0-canary.0 | 15.4.8 |
| `next` | npm | From 15.4.0-canary.0 | 15.4.8 |
| `next` | npm | From 15.5.0-canary.0 | 15.5.7 |
| `next` | npm | From 15.5.0-canary.0 | 15.5.7 |
| `next` | npm | From 16.0.0-canary.0 | 16.0.7 |
| `next` | npm | From 16.0.0-canary.0 | 16.0.7 |

## How do I fix GHSA-9qr9-h5gf-34mp?

Upgrade next to a fixed version for your release line: 15.0.5, 15.1.9, 15.2.6 or 15.3.6.

## Is GHSA-9qr9-h5gf-34mp being exploited?

There is no known exploitation of GHSA-9qr9-h5gf-34mp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9qr9-h5gf-34mp and fix it if it is affected.

What it is: GHSA-9qr9-h5gf-34mp is a code injection vulnerability in next, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-9qr9-h5gf-34mp in the wild and no public exploit code.

Affected packages and fixed versions:
- next (npm): affected from 14.3.0-canary.77; fixed in 15.0.5
- next (npm): affected from 14.3.0-canary.77; fixed in 15.0.5
- next (npm): affected from 15.1.0-canary.0; fixed in 15.1.9
- next (npm): affected from 15.1.0-canary.0; fixed in 15.1.9
- next (npm): affected from 15.2.0-canary.0; fixed in 15.2.6
- next (npm): affected from 15.2.0-canary.0; fixed in 15.2.6
- next (npm): affected from 15.3.0-canary.0; fixed in 15.3.6
- next (npm): affected from 15.3.0-canary.0; fixed in 15.3.6
- next (npm): affected from 15.4.0-canary.0; fixed in 15.4.8
- next (npm): affected from 15.4.0-canary.0; fixed in 15.4.8
- next (npm): affected from 15.5.0-canary.0; fixed in 15.5.7
- next (npm): affected from 15.5.0-canary.0; fixed in 15.5.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/GHSA-9qr9-h5gf-34mp/ (Markdown: https://insights.sbomify.com/GHSA-9qr9-h5gf-34mp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9qr9-h5gf-34mp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9qr9-h5gf-34mp/
Summaries are generated and may contain mistakes; the official description above is the record.