Vulnerability in agno (CVE-2026-35002)
Summary
Vulnerability in agno (CVE-2026-35002). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 2.3.24 or later.
Original description
The description as published by the source.
Agno versions prior to 2.3.24 contain an arbitrary code execution vulnerability in the model execution component that allows attackers to execute arbitrary Python code by manipulating the field_type parameter passed to eval(). Attackers can influence the field_type value in a FunctionCall to achieve remote code execution.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35002 has been found in agno.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade agno to 2.3.24 or later.
If unsure, ask your IT team or search "agno CVE-2026-35002" on the vendor's site.
CVE-2026-35002 (agno) — CWE-95 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.3.24 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-95) exists in agno.
Check the vendor advisory for the affected versions of agno.
Severity: Critical (CVSS 9.8/10). Successful exploitation can lead to full system takeover.
Update to 2.3.24.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'agno' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'agno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
agnoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade agno to 2.3.24ステージング環境で 2.3.24 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory disclosure@vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch disclosure@vulncheck.com
- web disclosure@vulncheck.com