Possible React Server Components Exploitation via Next-Action Header

PremiumReviewedSigma · Medium · v1
Category
webserver
Author
HuntRule
Published
2026-08-25
Updated
2026-08-28

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects inbound web requests carrying a Next-Action server action header together with crafted action parameter markers, the request shape used to trigger CVE-2025-55182 in React Server Components. Exploitation abuses the server action deserialization path to reach arbitrary command execution. Requests bearing this header alongside the action index syntax against a Next.js application warrant investigation for RCE attempts.

Related detections9 linkedT1190 — drag to rearrange
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Malicious Command Shell or PowerShell Spawned by Tomcat via Process Creation (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible TP-Link Command Injection via WlanNetworkRpm Endpoint (via webserver)
Malicious SharePoint ToolPane Exploitation via SignOut Referer
Suspicious Tomcat Session Deserialization Trigger via Crafted JSESSIONID
Malicious Tomcat Partial PUT of Session File via Content-Range Header
Malicious Ivanti Connect Secure Path Traversal Exploitation of CVE-2024-21887
Malicious MOVEit moveitisapi Exploitation Request via webserver
Possible React Server Components Exploitation via Next-Action Header
Pivot detection · T1190 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.