agno contains a SQL injection vulnerability
CVE-2026-10105 · GHSA-82m5-3pcp-hccq · published 2026-05-29 · updated 2026-07-02
- Severity
- High
- CVSS score
- 8.3
- Chance of exploitation (EPSS)
- 0.40%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
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.
No fixed release is listed yet for agno. Limit what it can reach, or stop using it until a fix ships, and follow the source advisory for updates.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| agno | PyPI | <= 2.6.5 | No fix yet |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.