Advisory record · GHSA-xfqj-4cr9-9gr5

GPTCache: File and image cache keys collide because BufferedReader.peek() only reads the buffered prefix

CVSS 2.0 LowEPSS 0.0008 · 1st percentile

Published by the GitHub Advisory Database at 4 Jun 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
gptcachePyPI<=0.1.44No fixed version yet
Identifiers
GHSA-xfqj-4cr9-9gr5 · CVE-2026-10812 · PYSEC-2026-3468
Weakness (CWE)
CWE-327 · CWE-328
Published
4 Jun 2026
Updated
23 Jul 2026

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.

Written 5 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 31 Oct 2026, 14:41 UTC First seen by agentprime
  2. 31 Oct 2026, 14:41 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.