<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloudflare-Workers on CuraSec</title><link>https://curasec.metacog.co.kr/tags/cloudflare-workers/</link><description>Recent content in Cloudflare-Workers on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 20 Aug 2026 11:39:11 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/cloudflare-workers/index.xml" rel="self" type="application/rss+xml"/><item><title>Remote Spectre Attack Leaks JWTs from Cloudflare Workers at 12 bps</title><link>https://curasec.metacog.co.kr/insights/2026-08-20-cloudflare-workers-spectre-attack-leaks-jwt-from-co-located/</link><pubDate>Thu, 20 Aug 2026 11:39:11 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-20-cloudflare-workers-spectre-attack-leaks-jwt-from-co-located/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> If you process sensitive credentials or JWTs in Cloudflare Workers, audit whether those secrets could be exposed to co-tenant side-channel leakage; consider moving high-sensitivity auth operations off shared serverless platforms or reducing secret lifetimes in Workers.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> Novel remote Spectre variant demonstrating cross-tenant memory leakage in shared serverless runtimes; no IOCs or detection surface exist yet, but the technique advances the threat model for cloud-hosted execution environments.&lt;/li>
&lt;li>&lt;strong>Leader — Learn:&lt;/strong> Research confirms meaningful cross-tenant isolation risks in shared serverless platforms; useful context for vendor risk conversations with Cloudflare and for evaluating where sensitive auth tokens are processed in your stack.&lt;/li>
&lt;/ul></description></item></channel></rss>