Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-mwv6-3258-q52c

HIGH

Next Vulnerable to Denial of Service with Server Components

Published
Dec 11, 2025
Updated
Feb 4, 2026
Affected
10 pkgs
Patched
10 / 10
Exploits
None indexed

Blast Radius

10 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

nextnpm
44.2Mdownloads / week

Description

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 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-55184.

A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.

Affected Packages

10 total 10 fixed
EcosystemPackageVulnerable rangeFix
📦npmnext13.3.0&&< 14.2.3414.2.34
📦npmnext15.0.0-canary.0&&< 15.0.615.0.6
📦npmnext15.1.1-canary.0&&< 15.1.1015.1.10
📦npmnext15.2.0-canary.0&&< 15.2.715.2.7
📦npmnext15.3.0-canary.0&&< 15.3.715.3.7
📦npmnext15.4.0-canary.0&&< 15.4.915.4.9

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for next. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update next to 14.2.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mwv6-3258-q52c is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-mwv6-3258-q52c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-mwv6-3258-q52c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability affects certain React packages for versions 19.0.0, 19.0.1, 19.1.0, 19.1.1, 19.1.2, 19.2.0, and 19.2.1 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-55184](https://www.cve.org/CVERecord?id=CVE-2025-55184). A malicious HTTP request can be crafted and sent to any App Router endpoint that, when deserialized, can cause the server process to hang and consume CPU. This can result in denial of service in unpatched environments.
O3 Security · Impact-Aware SCA

Is GHSA-mwv6-3258-q52c in your dependencies?

O3 detects GHSA-mwv6-3258-q52c across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.