GHSA-9qr9-h5gf-34mp — next
CRITICALGHSA-9qr9-h5gf-34mp is a critical-severity (CVSS 10) vulnerability in next. A fix is available for next — see the affected versions and patch details below.
Next.js is vulnerable to RCE in React flight protocol
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
nextnpmDescription
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | next | ≥ 14.3.0-canary.77&&< 15.0.5 | 15.0.5npm install next@15.0.5 |
| 📦npm | next | ≥ 15.1.0-canary.0&&< 15.1.9 | 15.1.9npm install next@15.1.9 |
| 📦npm | next | ≥ 15.2.0-canary.0&&< 15.2.6 | 15.2.6npm install next@15.2.6 |
| 📦npm | next | ≥ 15.3.0-canary.0&&< 15.3.6 | 15.3.6npm install next@15.3.6 |
| 📦npm | next | ≥ 15.4.0-canary.0&&< 15.4.8 | 15.4.8npm install next@15.4.8 |
| 📦npm | next | ≥ 15.5.0-canary.0&&< 15.5.7 | 15.5.7npm install next@15.5.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update next to 15.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9qr9-h5gf-34mp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9qr9-h5gf-34mp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-9qr9-h5gf-34mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9qr9-h5gf-34mp in your dependencies?
O3 Security finds GHSA-9qr9-h5gf-34mp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.