# CVE-2026-32247: Graphiti vulnerable to Cypher Injection via unsanitized node_labels in search filters

> Attackers can execute arbitrary Cypher queries via unsanitized node labels in search filters, potentially compromising data integrity and confidentiality.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-gg5m-55jj-8m5g, PYSEC-2026-2504

## What is CVE-2026-32247?

CVE-2026-32247 is a high-severity code injection vulnerability in getzep graphiti, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Graphiti is a framework for building and querying temporal context graphs for AI agents. Graphiti versions before 0.28.2 contained a Cypher injection vulnerability in shared search-filter construction for non-Kuzu backends. Attacker-controlled label values supplied through SearchFilters.node_labels were concatenated directly into Cypher label expressions without validation. In MCP deployments, this was exploitable not only through direct untrusted access to the Graphiti MCP server, but also through prompt injection against an LLM client that could be induced to call search_nodes with attacker-controlled entity_types values. The MCP server mapped entity_types to SearchFilters.node_labels, which then reached the vulnerable Cypher construction path. Affected backends included Neo4j, FalkorDB, and Neptune. Kuzu was not affected by the label-injection issue because it used parameterized label handling rather than string-interpolated Cypher labels. This issue was mitigated in 0.28.2.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-32247?

3 open source packages ship an affected version, including graphiti-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `graphiti-core` | PyPI | All versions | 0.28.2 |
| `graphiti-core` | PyPI | All versions | 0.28.2 |
| `graphiti-core` | PyPI | All versions | 0.28.2 |

Products: Getzep Graphiti.

## How do I fix CVE-2026-32247?

Upgrade graphiti-core to 0.28.2 or later.

## Is CVE-2026-32247 being exploited?

There is no known exploitation of CVE-2026-32247 in the wild and no public exploit code.

Public exploit code:

- Cypher injection in Graphiti via unsanitized node_labels — CVE-2026-32247 / CVSS 8.1 (github_poc): https://github.com/romain-deperne/CVE-2026-32247

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32247 and fix it if it is affected.

What it is: CVE-2026-32247 is a high-severity code injection vulnerability in getzep graphiti, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32247 in the wild and no public exploit code.

Affected packages and fixed versions:
- graphiti-core (PyPI): affected all versions; fixed in 0.28.2
- graphiti-core (PyPI): affected all versions; fixed in 0.28.2
- graphiti-core (PyPI): affected all versions; fixed in 0.28.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32247/ (Markdown: https://insights.sbomify.com/CVE-2026-32247/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32247
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32247
- OSV: https://osv.dev/vulnerability/CVE-2026-32247

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32247/
Summaries are generated and may contain mistakes; the official description above is the record.