agno
Affected
- introduced
0, fixed2.3.24(ecosystem)
Fixed versions
2.3.24
Fix
- Fixed version
2.3.24pip install --upgrade agno==2.3.24
Advisory
Also known as: CVE-2026-35002, GHSA-77rh-m34w-rv36, PYSEC-2026-256
Agno: Arbitrary code execution via eval() on field_type in FunctionCall
Impact
Agno versions prior to 2.3.24 contain an arbitrary code execution vulnerability
in the model execution component. The field_type parameter on a FunctionCall
input field was passed to Python's built-in eval(), allowing an attacker who
could influence that value to execute arbitrary Python code in the Agno process.
This is a code injection flaw (CWE-95) with full impact to confidentiality,
integrity, and availability. CVSS 3.1 score: 9.3 (Critical).
Any deployment that exposes Agno to user-influenced FunctionCall inputs
(for example via an API, web UI, or untrusted tool/model output) is affected.
Patches
Fixed in Agno 2.3.24.
The unsafe eval() call was replaced with a fixed type_mapping dictionary
lookup, and field_type is now validated as either a known string key or an
already-resolved type object before use. See commit
cbf67552
(PR #5912).
All users should upgrade to 2.3.24 or later. The current release line (2.6.x)
includes the fix.
Workarounds
There is no safe workaround. Users who cannot upgrade should ensure no
untrusted input can reach the field_type parameter of FunctionCall
input fields, but upgrading is strongly preferred.
References
Critical Basis: The source's own band: CRITICAL
0, fixed 2.3.24 (ecosystem)2.3.24
2.3.24pip install --upgrade agno==2.3.24Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0