Next.js is vulnerable to RCE in React flight protocol
Published 3 Dec 2025 · Updated 10 Sept 2026
Affected packages
- Affected
- >=14.3.0-canary.77 <15.0.5
- Fixed in
- 15.0.5
npm install next@15.0.5- Affected
- >=15.1.0-canary.0 <15.1.9
- Fixed in
- 15.1.9
npm install next@15.1.9- Affected
- >=15.2.0-canary.0 <15.2.6
- Fixed in
- 15.2.6
npm install next@15.2.6- Affected
- >=15.3.0-canary.0 <15.3.6
- Fixed in
- 15.3.6
npm install next@15.3.6- Affected
- >=15.4.0-canary.0 <15.4.8
- Fixed in
- 15.4.8
npm install next@15.4.8- Affected
- >=15.5.0-canary.0 <15.5.7
- Fixed in
- 15.5.7
npm install next@15.5.7- Affected
- >=16.0.0-canary.0 <16.0.7
- Fixed in
- 16.0.7
npm install next@16.0.7Details
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.
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
Is GHSA-9qr9-h5gf-34mp in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.