Cloudflare KV Cache Bug Leaks Other Users' Prompts into GLM-5.3 Answers
11/05/2026 — 11/05, 21:20·1 sources (all)·1 reports (all)
Key takeaways
- Cloudflare disclosed on October 26 that a KV cache accounting bug in the GLM-5.3 model on Workers AI caused 155 responses to read content le…
Background & analysis
Some users of Cloudflare's GLM-5.3 model on Workers AI received answers stitched partly from someone else's prompt during the summer of 2026, according to a November 5, 2026 article on DEV Community. The article, based on Cloudflare's own disclosure, says a memory bookkeeping error in the KV cache let 155 responses read pages a previous customer had left behind. The leak window ran from August 27 to September 9, 2026, and only prompts longer than 681,280 tokens were affected. The article states that no password was stolen. Cloudflare published a coordinated disclosure on October 26. The publicly available material provides no further details on remediation or follow-up, so the episode appears to rest on the disclosure itself.
AI-generated from 1 reports · updated 6 hours ago
- Heat index
- 82
- All sources
- 1
- All reports
- 1
- First seen
- 7 hours ago
Reports on this story headlines open the original
Cloudflare disclosed on October 26 that a KV cache bookkeeping bug in its GLM-5.3 model on Workers AI let 155 responses pull in content left behind by other customers. The leak window ran from August 27 to September 9 and only prompts longer than 681,280 tokens were affected; no passwords were stolen.
DEV Community · AIAI score 61
Other stories people are talking about
- Heat index 144SurgeCloudflare: Agent Traffic Leaves Websites Unable to Identify Users2 sources
- Heat index 43Developer deploys personal AI reminder bot on Cloudflare free tier1 sources
- Heat index 840OpenAI ships Images 2.6 with GIF and SVG output15 sources
- Heat index 675OpenAI says its cyber model pipeline confirmed 1,724 Linux kernel flaws and generated 948 privilege-escalation exploits11 sources
- Heat index 642RisingOpenAI GPT-5.6 Brings Major Agentic and Computer Use Upgrades13 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion