Cloudflare Reveals Cross-Tenant AI Data Exposure in GLM-5.3 Model
Cloudflare AI leak involved the GLM‑5.3 model hosted on Cloudflare Workers AI, not Cloudflare's broader infrastructure. According to Cloudflare's October 26, 2026 incident report, a bug caused 155 AI responses to contain fragments of data from other customers' prompts and sessions. turn1search2
- The affected model was @cf/zai-org/glm-5.3, available through orkers AI. turn1search4
- Between August 27 and September 9, 2026, some users who submitted extremely large rompts received responses containing data from other tenants. turn1search4
- Cloudflare states that only 155 responses were affected, all involving prompts larer than 681,280 tokens. turn1search7
- The issue was reported by security researcher https://www.office.com/serch?q=Gadi+Evron&EntityRepresentationId=c867d1ae-a2e7-880f-bc7d-ba119ebaf4e5 of Knostic through HackerOne. turn1search4
- A configuration mismatch where the model was deployed with a 1,048,576-token contet window but the underlying KV cache could hold only 681,280 tokens. turn1search7
- A bug in the SGLang inference engine that allowed ovr-length requests to access stale KV-cache data from previous users. turn1search4
- The vulnerability was fixed on September 9, 2026, and additional hardening was addd to SGLang. turn1search7
For security teams, this is a notable example of an AI multi-tennt isolation failure. The bug did not stem from the model itself, but from the AI-serving infrastructure that manages shared GPU memory and KV caches. Similar issues are becoming an emerging risk area for organizations consuming hosted AI services. turn1search2
For defenders: If your organization uses Cloudflare Workers AI and specifically use GLM‑5.3 during the affected period, it would be prudent to review whether any highly sensitive data was submitted in very large prompts, though Cloudflare's investigation found no signs of active abuse.

Comments
Post a Comment