# CVE-2026-108816: agno-agi agno PythonTools python.py run_python_code code injection

> Remote attackers can execute arbitrary Python code via the run_python_code function in the agno library, requiring immediate attention from users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jxpq-35pp-m3rc

## What is CVE-2026-108816?

CVE-2026-108816 is a medium-severity code injection vulnerability in agno-agi agno, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in agno-agi agno up to 3.0.6. Affected by this vulnerability is the function run_python_code of the file python.py of the component PythonTools. The manipulation of the argument code results in code injection. The attack can be launched remotely. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-108816 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108816 is a medium-severity code injection vulnerability in agno-agi agno, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108816 exists.

Affected product: agno-agi agno. 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-108816/ (Markdown: https://insights.sbomify.com/CVE-2026-108816/index.md)
```

## Sources

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

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