创建

登录 ReadmeX

或

了解我们如何处理你的信息: 隐私政策

ReadmeX

陪你读懂 AI 动态

今天,想先了解什么?

选一份动态总结,或直接聊聊你的问题。

社区和关注动态总结只属于你自己。

资讯

Cloudflare披露GLM-5.3跨请求数据泄露

AI 总结

Cloudflare表示,2026年8月27日至9月9日,Workers AI上的GLM-5.3共有155次回应混入其他客户的请求数据。事故由部署配置不匹配与SGLang处理超长请求及陈旧KV缓存状态的漏洞共同导致,受影响回应均对应长度超过681,280个token的提示。Cloudflare于9月9日完成修复并恢复模型,并建议SGLang运营方升级至v0.5.22或更高版本。

深度见解

这起事件暴露了生产级AI服务栈中的租户隔离缺陷,而Cloudflare公布的配置修复和引擎补丁也为其他Workers AI及SGLang运营方提供了明确的处置依据。

On September 8, 2026, we were alerted by a security researcher, Gadi Evron from Knostic, to a tenant isolation issue affecting the GLM-5.3 Workers AI model (@cf/zai-org/glm-5.3) starting on August 27, 2026. We have remediated the issue, and we restored the model on September 9. We have confirmed that no other model hosted on Workers AI was affected.

Between August 27 and September 9, a small number of customers using the GLM 5.3 Workers AI model received responses that contained data from other customers' requests made to the same model shortly before theirs. In total, 155 responses were affected, all to prompts longer than 681,280 tokens.

After excluding our own testing and the researcher's, the requests we identified are consistent in timing and volume with ordinary long-context use, not with someone repeatedly exploiting the bug. We found no evidence of deliberate exploitation.

Today we are publishing this report alongside a post from SGLang, the open-source inference engine that we use, as a coordinated disclosure.This post describes the bug that caused this issue, our response timeline, and the subsequent hardening we have conducted on our production SGLang deployments. We also detail our continued efforts with the upstream maintainers of SGLang to address this and similar bugs.

#Cloudflare#GLM-5.3#Workers AI#SGLang#Z.ai#Knostic

原文约 16 分钟读完阅读原文
群聊

还没有评论,来说说你的看法。