CVE-2026-10812

LOWPre-NVD 3.63.6
EchelonGraph scoreMEDIUM confidence

Score 3.6 from GitHub Security Advisory (severity: LOW) published 2026-06-04. a secondary CVSS source baseline 3.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.6
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.6
EG Score
3.6(medium)
EPSS
0.1%
KEV
Not listed

Published

June 4, 2026

Last Modified

June 4, 2026

Vendor Advisories for CVE-2026-10812(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 13:50 UTCEG score recompute
  2. 2026-07-11 13:50 UTCGHSA enrichment
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-08 15:15 UTCEPSS rescore
  6. 2026-07-08 09:54 UTCEG score recompute
  7. 2026-07-08 09:54 UTCGHSA enrichment
  8. 2026-07-07 13:46 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-03 19:19 UTCEG score recompute
  11. 2026-07-03 19:19 UTCGHSA enrichment
  12. 2026-06-30 02:52 UTCEG score recompute
  13. 2026-06-30 02:52 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-26 22:55 UTCEG score recompute
  17. 2026-06-26 22:55 UTCGHSA enrichment
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-23 18:47 UTCEG score recompute
  20. 2026-06-23 18:47 UTCGHSA enrichment
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 29 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-20 12:10 UTCEG score recompute
  3. 2026-06-20 12:10 UTCGHSA enrichment
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-17 06:09 UTCEG score recompute
  7. 2026-06-17 06:09 UTCGHSA enrichment
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-15 17:48 UTCEPSS rescore
  10. 2026-06-14 23:18 UTCEPSS rescore
  11. 2026-06-14 02:12 UTCEG score recompute
  12. 2026-06-14 02:12 UTCGHSA enrichment
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-10 22:18 UTCEPSS rescore
  16. 2026-06-10 22:17 UTCEG score recompute
  17. 2026-06-10 22:17 UTCGHSA enrichment
  18. 2026-06-10 13:22 UTCEPSS rescore
  19. 2026-06-08 14:17 UTCEPSS rescore
  20. 2026-06-08 14:17 UTCEPSS rescore
  21. 2026-06-07 18:21 UTCEG score recompute
  22. 2026-06-07 18:21 UTCGHSA enrichment
  23. 2026-06-07 15:25 UTCEPSS rescore
  24. 2026-06-07 15:24 UTCEPSS rescore
  25. 2026-06-06 13:47 UTCEPSS rescore
  26. 2026-06-06 13:47 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-05 22:47 UTCEPSS rescore
  29. 2026-06-04 14:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-10812?
CVE-2026-10812 is a low vulnerability published on June 4, 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…
When was CVE-2026-10812 disclosed?
CVE-2026-10812 was first published in the National Vulnerability Database on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10812 actively exploited?
CVE-2026-10812 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10812?
CVE-2026-10812 has a CVSS v3 base score of 3.6 (NVD).
How do I remediate CVE-2026-10812?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10812, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10812

Explore →

Is Your Infrastructure Affected by CVE-2026-10812?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.