"RCE is a legacy PHP and Java problem." That comfort blanket is gone — CVE-2025-55182 is a CVSS 10.0 RCE in modern React Server Components.
For years the assumption was: we use modern React/Next.js, so classic Remote Code Execution is someone else's problem.
That illusion is gone. CVE-2025-55182 is a critical (CVSS 10.0) deserialization RCE in React Server Components. It affects Next.js App Router apps on 15.x and 16.x, and an app can be exposed even without defining its own Server Actions. CISA added it to the Known Exploited Vulnerabilities catalog on 5 December 2025, so it is being exploited in the wild. Patch to a fixed release (15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7, and React 19.0.1 / 19.1.2 / 19.2.1).
The community shipped Burp Suite detection plugins quickly:
- https://github.com/Pizz33/CVE-2025-55182-burpscanner
- https://github.com/Cr4at0r/Next.js-RCE-Scanner-BurpSuite-Extension-
Here's the mental model every fullstack and AppSec engineer needs.
The paradigm shift: frontend meets backend
In classic architectures the frontend was static HTML/JS and the backend a separate, explicitly-routed API. With React Server Components, functions declared on the server are invoked straight from client component code via Server Actions, and the framework quietly handles serialization, transport, deserialization and execution of complex data structures.
Where it breaks
1. Opaque deserialization. Triggering a Server Action serializes objects, promises and internal state across an HTTP POST with special headers (e.g. Next-Action). A flaw in how the server reconstitutes those objects can lead to prototype pollution, object injection or code execution.
2. Hidden endpoints. "Nobody can call it, it has no button" is false. Every exported server action gets a deterministic ID that can be hit with a raw HTTP request.
3. Authorization blind spots. Because actions feel like local function calls, engineers forget to check the session and permissions at the top of the action.
How to secure modern SSR
- Treat every server action as a public endpoint. Validate every argument with a strict schema (Zod).
- Verify identity explicitly inside the action, before touching any database or internal API.
- Patch aggressively. Server frameworks are as security-critical as your kernel.
- Automate detection. Wire a scanner for CVE-2025-55182 into staging so an outdated framework version never reaches production.
Seeing more framework-specific findings in your tests lately? Let's compare notes below.
Top comments (0)