# A revisit of remote Spectre attacks on Cloudflare Workers

[Cloudflare](https://yomu.fyi/company/cloudflare) · Martin Schwarzl · Aug 19, 2026

**Type:** Problem & solution

## Summary

Cloudflare reassessed remote Spectre attack feasibility within Cloudflare Workers production workloads to evaluate defenses against modern stabilization techniques. The experimental proof of concept bypassed Dynamic Process Isolation (DyPrIs) by keeping invocations alive using WebSocket traffic, which also diluted hardware performance counter ratios below detection thresholds. By combining branch mistraining, cache line eviction, and speculative type confusion, researchers transiently accessed out-of-bounds memory via raw 64-bit TypedArray backing store pointers. This attack demonstrated cross-tenant data leakage reaching up to 12 bit/s with over 99% accuracy in production. In response, Cloudflare mitigated the vulnerability by integrating the V8 memory sandbox, deploying Memory Protection Keys for hardware-assisted in-process isolation, and redesigning DyPrIs to monitor active long-lived executions.

## Context

Cloudflare Workers isolates thousands of tenants inside shared operating-system processes using V8 isolates. Although mitigations such as restricted timers, disabled multithreading, and Dynamic Process Isolation (DyPrIs) were deployed, advancements in remote Spectre exploitation raised concerns that attackers could bypass defenses and achieve cross-tenant memory disclosure.

## Approach / What changed

Cloudflare evaluated an updated remote Spectre proof of concept using speculative type confusion against raw 64-bit TypedArray backing store pointers. After identifying detection blind spots in DyPrIs, Cloudflare deployed the V8 sandbox, introduced Memory Protection Keys (MPK) to restrict cross-isolate memory access in hardware, and updated DyPrIs to evaluate long-lived executions.

## Takeaways

- The experimental remote Spectre attack leaked data in production at up to 12 bit/s with greater than 99% accuracy despite restricted local timers and CPU load.
- WebSocket keep-alive messages maintained open Worker invocations for hours, evading post-invocation DyPrIs isolation and inflating iTLB activity to mask branch misprediction ratios.
- Cloudflare hardened the runtime by implementing the V8 sandbox, hardware-enforced memory isolation using Memory Protection Keys, and real-time DyPrIs monitoring for active workloads.

**Tags:** [Architecture](https://yomu.fyi/topic/architecture), [Performance](https://yomu.fyi/topic/performance), [Serverless](https://yomu.fyi/topic/serverless)

[Read original post](https://blog.cloudflare.com/revisiting-spectre-attacks-on-workers)