What happened
Cloudflare: WAF change for a React vulnerability hit a latent Lua bug. Scope: Partial global (~28% of HTTP traffic).
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Cloudflare: WAF change for a React vulnerability hit a latent Lua bug. Scope: Partial global (~28% of HTTP traffic).
Severe storm
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Cloudflare: WAF change for a React vulnerability hit a latent Lua bug. Scope: Partial global (~28% of HTTP traffic).
Cloudflare HTTP / WAF (older FL1 proxy).
14 catalogued services run on Cloudflare (inferred). Hit: Partial global (~28% of HTTP traffic).
Resolved after 25m.
Center: Cloudflare. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
Correlation is not causation
Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.
The issue was not caused, directly or indirectly, by a cyber attack on Cloudflare’s systems or malicious activity of any kind. Instead, it was triggered by changes being made to our body parsing logic while attempting to detect and mitigate an industry-wide vulnerability disclosed this week in React Server Components.
Official window 08:47–09:12 UTC (~25 minutes). About 28% of HTTP traffic served by Cloudflare was in the affected subset.
Verbatim excerpt from Cloudflare outage on December 5, 2025.
100% similar · same provider
New DDoS rule exposed a latent rate-limiting bug
Config push
90% similar · same provider
Network configuration change took 19 data centers offline
Config push
70% similar · same provider
Bot Management feature file doubled and crashed traffic-routing software
Config pushCapacityCascade
Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.
Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Cloudflare.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Cloudflare in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/cf-waf-lua-2025-12-05/"><img src="https://www.chyp.ai/dissect/m/cf-waf-lua-2025-12-05/card.svg" alt="WAF change for a React vulnerability hit a latent Lua bug · ORBIT Outage Dissector" width="600"></a>