Cache poisoning via buffered-prefix key collisions
Published Jun 4, 2026 · Updated Jun 4, 2026
Cache-key collision in Zilliz GPTCache 0.1.0 through 0.1.44 allows local users to poison cached file or image responses. The get_file_bytes, get_input_str, and get_image_question paths derive cache inputs from BufferedReader.peek(), which reads only the buffered prefix rather than the full content. Local access must supply two streams sharing roughly the first 8192 bytes and the same question; GPTCache can then return another stream's cached answer without evaluating its remaining content.
Summary
What happened
Cache-key collision in Zilliz GPTCache 0.1.0 through 0.1.44 allows local users to poison cached file or image responses. The get_file_bytes, get_input_str, and get_image_question paths derive cache inputs from BufferedReader.peek(), which reads only the buffered prefix rather than the full content. Local access must supply two streams sharing roughly the first 8192 bytes and the same question; GPTCache can then return another stream's cached answer without evaluating its remaining content.
The record
- CVE
- CVE-2026-10812
- Published
- Jun 4, 2026
- Updated
- Jun 4, 2026
- Vendor
- Zilliz
- Product
- GPTCache
- Classifications
- CWE-327, CWE-328, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 4, 2026CVE publishedPublication date reported by the CVE source.
- Jun 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
- Affected versionversion=0.1.1
- Affected versionversion=0.1.10
- Affected versionversion=0.1.11
- Affected versionversion=0.1.12
- Affected versionversion=0.1.13
- Affected versionversion=0.1.14
- Affected versionversion=0.1.15
- Affected versionversion=0.1.16
- Affected versionversion=0.1.17
- Affected versionversion=0.1.18
- Affected versionversion=0.1.19
- Affected versionversion=0.1.2
- Affected versionversion=0.1.20
- Affected versionversion=0.1.21
- Affected versionversion=0.1.22
- Affected versionversion=0.1.23
- Affected versionversion=0.1.24
- Affected versionversion=0.1.25
- Affected versionversion=0.1.26
- Affected versionversion=0.1.27
- Affected versionversion=0.1.28
- Affected versionversion=0.1.29
- Affected versionversion=0.1.3
- Affected versionversion=0.1.30
- Affected versionversion=0.1.31
- Affected versionversion=0.1.32
- Affected versionversion=0.1.33
- Affected versionversion=0.1.34
- Affected versionversion=0.1.35
- Affected versionversion=0.1.36
- Affected versionversion=0.1.37
- Affected versionversion=0.1.38
- Affected versionversion=0.1.39
- Affected versionversion=0.1.4
- Affected versionversion=0.1.40
- Affected versionversion=0.1.41
- Affected versionversion=0.1.42
- Affected versionversion=0.1.43
- Affected versionversion=0.1.44
- Affected versionversion=0.1.5
- Affected versionversion=0.1.6
- Affected versionversion=0.1.7
- Affected versionversion=0.1.8
- Affected versionversion=0.1.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- BufferedReader.peek collision reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo