Summaries
Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.
Showing 1-2 of 2 results
| Date | Provider | Score | Summary |
|---|---|---|---|
| 20 Aug 2026, 3:02 AM | The Hacker News | 7.0 | Cloudflare Workers Spectre Attack Leaks JWT From Co-Located Worker at 12 Bits/Second
Security researchers demonstrated a remote Spectre attack on Cloudflare Workers that leaked a JWT from a co-located Worker at 12 bits/second, 360x faster than a 2021 proof-of-concept. The attack exploited V8 isolate co-location within the same OS process, using WebSocket traffic as a remote timing source and Durable Objects to keep an isolate alive for 5-20+ hours, bypassing Cloudflare's Dynamic Process Isolation before it could trigger. Cloudflare reports the attack is now mitigated via V8 Sandbox integration and Memory Protection Keys, with no evidence of active exploitation in three years. Why: If you ship on Cloudflare Workers with Durable Objects or WebSockets, this reveals that language-level V8 isolation is not equivalent to process isolation, and that long-lived Durable Object invocations created a window where DyPrIS never fired. The mitigations are deployed, but the architectural tradeoff—shared-process multi-tenancy for low startup latency—remains inherent to the platform. Review whether sensitive tokens like JWTs belong in Worker memory at all, and consider whether your threat model accounts for co-tenant side-channel risk on edge platforms that use isolate-based isolation rather than full process boundaries. |
| 20 Aug 2026, 12:00 AM | Cloudflare Blog | 6.0 | A revisit of remote Spectre attacks on Cloudflare Workers
Cloudflare internally retested remote Spectre attacks against Workers using newer stabilization techniques and found a limitation in their Dynamic Process Isolation (DyPrIs) defense, achieving reliable cross-tenant memory leakage at 12 bit/s with 99% accuracy in production. They have since mitigated it by integrating the V8 Sandbox and an in-process isolation mechanism. No indicators of active exploitation were found over the past three years. Why: If you run multi-tenant workloads on Cloudflare Workers or similar V8-isolate platforms, this confirms speculative-execution side channels remain a real cross-tenant risk even under production noise, and that platform-level mitigations are evolving—so don't assume language-level heap isolation alone protects sensitive data across tenants. |