# CVE-2025-6101: letta-ai letta interface.py function_message eval injection

> Attackers can execute arbitrary code via improper neutralization in the function_message interface of the letta-ai library.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-f28h-v254-c2wx

## What is CVE-2025-6101?

CVE-2025-6101 is a medium-severity code injection vulnerability in letta-ai letta, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in letta-ai letta up to 0.4.1. Affected is the function function_message of the file letta/letta/interface.py. The manipulation of the argument function_name/function_args leads to improper neutralization of directives in dynamically evaluated code. The exploit has been disclosed to the public and may be used.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-6101?


## How do I fix CVE-2025-6101?

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

## Is CVE-2025-6101 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6101 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6101 and fix it if it is affected.

What it is: CVE-2025-6101 is a medium-severity code injection vulnerability in letta-ai letta, published on 16 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6101 exists.

Affected product: letta-ai letta. 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-2025-6101/ (Markdown: https://insights.sbomify.com/CVE-2025-6101/index.md)
```

## Sources

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

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