Vulnerability in gptcache (CVE-2026-10812)
Summary
Vulnerability in gptcache (CVE-2026-10812). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-10812 has been found in gptcache.
Risk of unauthorized operations or information disclosure. CVSS score: 3.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "gptcache CVE-2026-10812" on the vendor's site.
CVE-2026-10812 (gptcache) — CWE-327 / CVSS v3 3.6
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-327) exists in gptcache.
Check the vendor advisory for the affected versions of gptcache.
Severity: Low (CVSS 3.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gptcache' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'gptcache' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gptcacheを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- report github.com
- report vuldb.com
- web github.com