# CVE-2026-10105: agno 2.6.5 SQL Injection via ClickHouse delete_by_metadata()

> Attackers can inject SQL via metadata in agno's ClickHouse backend to delete or extract data, requiring library upgrades.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **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:** 29 May 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-82m5-3pcp-hccq, PYSEC-2026-2333

## What is CVE-2026-10105?

CVE-2026-10105 is a high-severity SQL injection vulnerability in agno-agi agno, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

agno 2.6.5 contains a SQL injection vulnerability in the ClickHouse vector database backend that allows attackers to inject arbitrary SQL expressions by supplying malicious metadata keys and values to the delete_by_metadata() method. Attackers can exploit the unsafe f-string interpolation in clickhousedb.py to delete all rows, target specific rows, or extract information through error-based or blind SQL injection techniques.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

3 open source packages ship an affected version, including agno.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `agno` | PyPI | All versions to 2.6.5 | None |
| `agno` | PyPI | All versions to 2.6.5 | None |
| `agno` | PyPI | All versions to 2.6.5 | None |

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

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

## Is CVE-2026-10105 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10105 is a high-severity SQL injection vulnerability in agno-agi agno, published on 29 May 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-10105 exists.

Affected packages and fixed versions:
- agno (PyPI): affected all versions up to 2.6.5; no fix listed
- agno (PyPI): affected all versions up to 2.6.5; no fix listed
- agno (PyPI): affected all versions up to 2.6.5; no fix listed

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

## Sources

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

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