Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
GPTCache versions up to and including 0.1.44 are affected. An attacker with local access who can supply crafted file or image input can cause different inputs to produce colliding cache keys, because the key is built from only the buffered prefix of the data. The source describes the attack as high complexity and difficult to exploit, and says a public exploit exists. No fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 2.0 | Low | 4.0 | CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P | CNA (VulDB) |
- CISA KEV Not listed.
- EPSS 0.0008, the 1st percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:41 UTC First seen by agentprime
- 31 Oct 2026, 14:41 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-xfqj-4cr9-9gr5
- OSV: GHSA-xfqj-4cr9-9gr5
- nvd.nist.gov/vuln/detail/CVE-2026-10812
- github.com/zilliztech/GPTCache/issues/684
- github.com/zilliztech/GPTCache/pull/678
- github.com/zilliztech/GPTCache
- vuldb.com/cve/CVE-2026-10812
- vuldb.com/submit/831636
- vuldb.com/vuln/368260
- vuldb.com/vuln/368260/cti