← Back
CVE-2026-32247
Vulnerability in graphiti-core (CVE-2026-32247)
Summary
vulnerability in graphiti-core (CVE-2026-32247). Confidential information can be exposed externally. Exploitable via ``SearchFilters.node_labels``. Mitigation: upgrade to `0.28.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-32247** has been found in graphiti-core.
Attackers can target a specific entry point like ``SearchFilters.node_labels`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade graphiti-core to **0.28.2** or later.
If unsure, ask your IT team or search "graphiti-core CVE-2026-32247" on the vendor's site.
CVE-2026-32247 (graphiti-core) — CWE-943 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `SearchFilters.node_labels` / `search_nodes` / `entity_types` / `group_ids`
Patched: `0.28.2` — apply immediately
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.
❓ What is the problem
**A vulnerability** (CWE-943) exists in graphiti-core. Attackers reach the vulnerable code path via ``SearchFilters.node_labels`` without authentication.
📍 Affected scope
graphiti-core — . Attack surface: `SearchFilters.node_labels` / `search_nodes` / `entity_types` / `group_ids`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **0.28.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'graphiti-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'graphiti-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `graphiti-core` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade graphiti-core to 0.28.2ステージング環境で 0.28.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
graphiti-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.28.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-32247
- advisory https://github.com/advisories/GHSA-gg5m-55jj-8m5g
- package https://github.com/getzep/graphiti
- package https://pypi.org/project/graphiti-core
- web https://github.com/getzep/graphiti/security/advisories/GHSA-gg5m-55jj-8m5g
- web https://github.com/getzep/graphiti/pull/1312
- web https://github.com/getzep/graphiti/commit/7d65d5e77e89a199a62d737634eaa26dbb04d037
- web https://github.com/getzep/graphiti/releases/tag/v0.28.2