Esc
SafetyEmerging

Cloudflare Patches GLM-5.3 KV Cache Data Leak in Workers AI

Is this a scandal?

Not yet — an early signal. Noise 42/100, holding steady, across 3 sources.

SCAND-346943as of Methodology
Cite this incident"Cloudflare Patches GLM-5.3 KV Cache Data Leak in Workers AI." SCAND.Ai incident SCAND-346943, noise 42/100 as of October 29, 2026. https://scand.ai/scandal/cloudflare-patches-glm53-kv-cache-leak-workers-ai
FORECASTForecast, not fact

Serverless AI providers will likely implement mandatory memory zeroing audits and publish third-party isolation attestations because enterprise clients demand verifiable tenant separation guarantees before deploying sensitive workloads.

42

Noise 42/100 — louder than 99% of tracked AI controversies.

AI-assisted analysis · How we work

Why it matters

This vulnerability highlights critical isolation failures in serverless AI inference, threatening enterprise adoption of shared GPU infrastructure for sensitive workloads.

Key points

  1. Cloudflare patched a cross-request KV cache exposure vulnerability in the GLM-5.3 Workers AI model.
  2. The flaw allowed residual memory from previous inference requests to be accessed by subsequent unrelated users.
  3. Security researchers identified the improper memory sanitization issue in the serverless multi-tenant environment.
  4. Cloudflare confirmed the fix and stated no evidence of active exploitation was detected.
  5. The incident exposes KV cache management as a critical but often overlooked attack surface in LLM serving.
  6. Only the GLM-5.3 model variant on Workers AI was affected by this specific isolation failure.

The story

Cloudflare has patched a critical security vulnerability in its Workers AI platform that allowed cross-request KV cache exposure in the GLM-5.3 model. Security researchers reported that improper memory isolation enabled subsequent API requests to access residual key-value cache data from previous users' sessions. The flaw potentially exposed sensitive prompts and model context between unrelated tenants on shared inference infrastructure. Cloudflare confirmed the issue and deployed a fix to enforce strict memory sanitization between requests. The company stated no evidence of malicious exploitation was found prior to remediation. This incident underscores persistent challenges in securing multi-tenant large language model serving environments. Industry experts note that KV cache management remains an under-audited attack surface in serverless AI deployments. The vulnerability affected only the GLM-5.3 model variant hosted on Workers AI. Cloudflare has since updated its security documentation regarding tenant isolation guarantees.

Who's involved

Critic
Security Researchers

Identified and reported the cross-request KV cache exposure flaw in GLM-5.3's multi-tenant implementation.

Defender
Cloudflare

Confirmed the vulnerability, deployed a fix for memory isolation, and stated no malicious exploitation occurred.

How the conversation shifted

opinion has hardened

Polarity (0–100) from the noise pipeline, sampled over time.

Join the Discussion

Discuss this story

Community comments coming in a future update

Be the first to share your perspective. Subscribe to comment.

Noise Level

Buzz42?Noise Score (0–100): how loud a controversy is. Composite of reach, engagement, star power, cross-platform spread, polarity, duration, and industry impact — with 7-day decay.
Decay: 98%
Reach
43
Engagement
78
Star Power
30
Duration
6
Cross-Platform
20
Polarity
50
Industry Impact
50

The timeline

  1. Cloudflare confirms patch deployment

    Company acknowledged the memory isolation issue and verified remediation was applied to Workers AI infrastructure.

  2. Vulnerability disclosed on Hacker News

    Post detailing cross-request KV cache exposure in GLM-5.3 garnered 155 responses from technical community.

The full record

Sources & methodology

Every claim above traces to these primary items. How we score →

The forecast

Serverless AI providers will likely implement mandatory memory zeroing audits and publish third-party isolation attestations because enterprise clients demand verifiable tenant separation guarantees before deploying sensitive workloads.

Forecast, not fact — an editorial estimate we score when this resolves.

You're up to date

That's the complete picture as of — nothing more to know right now. We'll update this page the moment it changes.

Follow this story

We keep this page current — no need to check back. We'll send the next real change to your inbox, nothing else.

Tracking this story since October 26, 2026.