Evidence · DiggingBeagle record
SGLang streaming session reuses physical KV cache across changed namespace on abort, creating cross-tenant cache ownership collision
SGLang maintainer/reporter issue describes streaming-session namespace changes that leave aliases to the same physical KV-cache slot across logical trees after abort and eviction. The issue raises a confidentiality and integrity risk but does not independently demonstrate tenant secret exfiltration or a fixed released version.
- Source role
- primary disclosure
Evidence record
SGLang maintainer/reporter issue describes streaming-session namespace changes that leave aliases to the same physical KV-cache slot across logical trees after abort and eviction. The issue raises a confidentiality and integrity risk but does not independently demonstrate tenant secret exfiltration or a fixed released version.
Claim-level citations (1)
- supportsSGLang streaming sessions could reuse one physical KV slot across separate cache namespaces: SGLang issue #49361 describes physical KV-cache aliasing across distinct streaming-session namespaces, with eviction capable of reusing a slot still referenced by another cache node.
GitHub issue #49361, namespace change, abort, eviction and use-after-free sequence