CVE-2026-10105

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

Score 8.3 from GitHub Security Advisory (severity: HIGH) published 2026-05-29. a secondary CVSS source baseline 8.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track*)
EG Risk 53/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
24.2%
KEV
Not listed

Published

May 29, 2026

Last Modified

July 21, 2026

Advisory Details (5)

Auto-updated Jun 3, 2026
🔬 Proof of concept available. No patch confirmed yet. Sources: github_pr.
generic🟡 PoC Available

[Vulnerability] SQL Injection in agno ClickHouse Vector Database via `delete_by_metadata` · Issue #7866 · agno-agi/agno · GitHub

https://github.com/agno-agi/agno/issues/7866
generic

agno 2.6.5 SQL Injection via ClickHouse delete_by_metadata() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/agno-sql-injection-via-clickhouse-delete-by-metadata
github_pr

fix(vectordb): eliminate SQL injection in ClickHouse delete_by_metadata

Upstream fix in progress (PR #7883 · agno-agi/agno, state=closed)

https://github.com/agno-agi/agno/pull/7883/changes/a0ec99305e782e68ba26f5966c53ad50b5f40132
github_pr

fix(vectordb): eliminate SQL injection in ClickHouse delete_by_metadata

Upstream fix in progress (PR #7883 · agno-agi/agno, state=closed)

https://github.com/agno-agi/agno/pull/7883/changes/26a7439b803c0ccc9a58ee53572d8088a678923f
github_pr

fix(vectordb): eliminate SQL injection in ClickHouse delete_by_metadata

Upstream fix in progress (PR #7883 · agno-agi/agno, state=closed)

https://github.com/agno-agi/agno/pull/7883

Vendor Advisories for CVE-2026-10105(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
pipagno—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
agno0.0.1 ... 2.6.5 (205 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 132 total refreshes for this CVE.

  1. 2026-07-23 03:04 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 02:28 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:02 UTCEPSS rescore
  9. 2026-07-16 01:59 UTCGHSA enrichment
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-14 14:08 UTCGHSA enrichment
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:12 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 17:33 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-08 17:25 UTCGHSA enrichment
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-08 15:15 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 02:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-02 16:05 UTCGHSA enrichment
  4. 2026-07-02 04:22 UTCGHSA enrichment
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 13:10 UTCGHSA enrichment
  8. 2026-07-01 01:32 UTCGHSA enrichment
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-30 00:57 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 12:50 UTCGHSA enrichment
  13. 2026-06-28 15:58 UTCGHSA enrichment
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 03:31 UTCGHSA enrichment
  18. 2026-06-27 15:54 UTCGHSA enrichment
  19. 2026-06-27 04:16 UTCGHSA enrichment
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 16:17 UTCGHSA enrichment
  22. 2026-06-26 02:27 UTCGHSA enrichment
  23. 2026-06-25 14:50 UTCGHSA enrichment
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 03:03 UTCGHSA enrichment
  26. 2026-06-24 15:25 UTCGHSA enrichment
  27. 2026-06-24 14:05 UTCEPSS rescore
  28. 2026-06-23 21:32 UTCEPSS rescore
  29. 2026-06-22 14:25 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-21 14:56 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 01:59 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-18 22:27 UTCGHSA enrichment
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 02:07 UTCGHSA enrichment
  39. 2026-06-17 17:53 UTCEPSS rescore
  40. 2026-06-17 14:30 UTCGHSA enrichment
  41. 2026-06-17 02:52 UTCGHSA enrichment
  42. 2026-06-16 17:52 UTCEPSS rescore
  43. 2026-06-16 15:14 UTCGHSA enrichment
  44. 2026-06-16 01:07 UTCGHSA enrichment
  45. 2026-06-15 17:48 UTCEPSS rescore
  46. 2026-06-15 13:29 UTCGHSA enrichment
  47. 2026-06-15 01:52 UTCGHSA enrichment
  48. 2026-06-14 23:18 UTCEPSS rescore
  49. 2026-06-14 14:15 UTCGHSA enrichment
  50. 2026-06-14 02:37 UTCGHSA enrichment
  51. 2026-06-13 23:00 UTCEPSS rescore
  52. 2026-06-13 23:00 UTCEPSS rescore
  53. 2026-06-13 14:59 UTCGHSA enrichment
  54. 2026-06-13 03:22 UTCGHSA enrichment
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-06-12 15:45 UTCGHSA enrichment
  57. 2026-06-12 04:06 UTCGHSA enrichment
  58. 2026-06-11 16:28 UTCGHSA enrichment
  59. 2026-06-11 14:00 UTCEPSS rescore
  60. 2026-06-11 04:49 UTCGHSA enrichment
  61. 2026-06-10 22:18 UTCEPSS rescore
  62. 2026-06-10 17:12 UTCGHSA enrichment
  63. 2026-06-10 13:22 UTCEPSS rescore
  64. 2026-06-10 05:33 UTCGHSA enrichment
  65. 2026-06-09 17:56 UTCGHSA enrichment
  66. 2026-06-09 06:19 UTCGHSA enrichment
  67. 2026-06-08 18:41 UTCGHSA enrichment
  68. 2026-06-08 14:17 UTCEPSS rescore
  69. 2026-06-08 14:17 UTCEPSS rescore
  70. 2026-06-08 07:04 UTCGHSA enrichment
  71. 2026-06-07 19:27 UTCGHSA enrichment
  72. 2026-06-07 15:25 UTCEPSS rescore
  73. 2026-06-07 15:24 UTCEPSS rescore
  74. 2026-06-07 07:50 UTCGHSA enrichment
  75. 2026-06-06 20:13 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-10105?
CVE-2026-10105 is a high vulnerability published on May 29, 2026. 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 deletebymetadata() method. Attackers can exploit the unsafe f-string interpolation in…
When was CVE-2026-10105 disclosed?
CVE-2026-10105 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10105 actively exploited?
CVE-2026-10105 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-10105?
CVE-2026-10105 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-10105?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10105, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10105

Explore →

Is Your Infrastructure Affected by CVE-2026-10105?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs