CVE-2026-10812 in GPTCache
Summary
by MITRE • 06/04/2026
A vulnerability was detected in zilliztech GPTCache up to 0.1.44. Affected by this issue is the function BufferedReader.peek of the file gptcache/processor/pre.py of the component Cache Key Handler. Performing a manipulation of the argument input_data["image"] results in use of weak hash. The attack must be initiated from a local position. The attack is considered to have high complexity. The exploitation is known to be difficult. The exploit is now public and may be used. The pull request to fix this issue awaits acceptance.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 06/04/2026
The vulnerability in zilliztech GPTCache version 0.1.44 resides within the Cache Key Handler component, specifically in the BufferedReader.peek function located at gptcache/processor/pre.py. This flaw represents a cryptographic weakness that manifests when the input_data["image"] parameter is manipulated, leading to the utilization of weak hashing mechanisms rather than secure cryptographic functions. The vulnerability is classified as a local privilege escalation vector, meaning that exploitation requires an attacker to have local system access or execution privileges within the target environment. The attack complexity is rated as high, indicating that successful exploitation demands specialized knowledge and significant effort to craft effective payloads. This complexity arises from the need to understand the specific implementation details of the hash function and the precise manipulation required to trigger the weak hashing behavior.
The technical flaw stems from improper handling of cryptographic operations within the cache key generation process, where the system fails to implement robust hashing algorithms when processing image data inputs. This weakness allows attackers to potentially predict or manipulate cache keys, which could lead to cache poisoning or denial of service conditions. The use of weak hash functions creates opportunities for attackers to craft specific inputs that produce predictable hash values, undermining the fundamental security assumptions of the caching mechanism. According to CWE classification, this vulnerability aligns with CWE-327, which addresses the use of weak cryptographic algorithms, and potentially CWE-20, which covers input validation issues that can lead to cryptographic weaknesses. The operational impact extends beyond simple cache manipulation, as compromised cache integrity can affect application performance, data consistency, and potentially enable more sophisticated attacks through cache-based information leakage.
The exploitation difficulty and current public availability of the exploit demonstrate that this vulnerability has reached a mature stage in the threat landscape, making it more likely to be weaponized by malicious actors. The fact that a pull request exists to address the issue indicates that the maintainers are aware of the problem, but the delay in acceptance creates a window of opportunity for attackers to leverage the vulnerability. Organizations using GPTCache versions up to 0.1.44 should consider immediate mitigation strategies, including upgrading to patched versions when available, implementing additional input validation layers, and monitoring for unusual cache behavior patterns. The local execution requirement provides some operational defense, but attackers with local access or those able to achieve local execution through other means can leverage this vulnerability to compromise the integrity of the caching system. Security teams should also consider implementing runtime monitoring to detect anomalous hash generation patterns that might indicate exploitation attempts, as well as reviewing access controls to minimize potential local attack surfaces. This vulnerability demonstrates the critical importance of cryptographic hygiene in application development and the need for regular security assessments of third-party components. The ATT&CK framework categorizes this issue under privilege escalation techniques, specifically targeting the cache management functionality to potentially establish persistent access patterns or manipulate application behavior through cache poisoning attacks.