# CVE-2026-31231: Code injection in n/a

> Attackers can execute arbitrary Python code on Cognee servers via the notebook API due to unsafe exec() usage, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-fcch-9ph8-q3p4

## What is CVE-2026-31231?

CVE-2026-31231 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cognee thru v0.4.0 contains a critical remote code execution vulnerability in its notebook cell execution API endpoint. The endpoint is designed to execute arbitrary Python code provided by the user, but it does so using the unsafe exec() function without any sandboxing, validation, or security controls. An attacker can exploit this by sending a specially crafted POST request containing malicious Python code to the execution endpoint. This leads to arbitrary code execution on the Cognee server with the privileges of the server process, allowing complete compromise of the system.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

No fix has been published for CVE-2026-31231 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31231 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31231 is a critical code injection vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31231 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-31231/ (Markdown: https://insights.sbomify.com/CVE-2026-31231/index.md)
```

## Sources

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

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