CVE-2025-66478
Not confirmed exploited. 1 of 8 rule sources name it.
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Public exploits
1 found- MetasploitUnauthenticated RCE in React Server Components (React2Shell)2025-12-03 · exploit · rank Excellent · has check
Links are to third-party code: never run it outside an isolated lab.
Timeline
- 2025-12-03Metasploit module publishedUnauthenticated RCE in React Server Components (React2Shell)
- 2025-12-04F5 ships a ruleReact Server Components RCE
Vendor statements
QuotedCloudflareWAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The feed holds only the latest 25 changes, so history builds up from the day we started reading it.
F5Attack signatures (Distributed Cloud WAF)
First dated 2025-12-04.
Added: signature 200204048 "React Server Components RCE" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
Updated: signature 200204048 "React Server Components RCE" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
Updated: signature 200204050 "Next.js RSC Remote Code Execution" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.