Quick answers
- Is CVE-2026-35002 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35002 being exploited in the wild.
- How severe is CVE-2026-35002?
- Critical severity, with a CVSS score of 9.8, published 2 April 2026.
- Which products and versions are affected?
- Agno prior to 2.3.24; agno (PyPI) < 2.3.24, ECOSYSTEM:introduced=0,fixed=2.3.24.
- Is there a fix for CVE-2026-35002?
- Yes. agno (PyPI): upgrade to 2.3.24 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35002 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-35002?
- Check whether you run Agno or agno (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- agno (PyPI): upgrade to 2.3.24 or later
pip install "agno>=2.3.24"
Technical details
An eval injection vulnerability (CWE-95) exists in Agno's model execution component due to the unsafe use of the Python eval() function. The vulnerability is located in the handling of the field_type parameter within a FunctionCall. A remote, unauthenticated attacker can influence this parameter to execute arbitrary Python code in the context of the application. The issue was addressed in version 2.3.24 by replacing the dynamic eval() call with a secure dictionary-based type mapping.
Affected products
- Agno Agno prior to 2.3.24
Identifiers
- CVE-2026-35002
- GHSA-77rh-m34w-rv36
- GHSA-m4w4-3r8h-jw98
- PYSEC-2026-256
Timeline
- 2026-01-08: patched: Version 2.3.24 released
- 2026-04-02: advisory: Initial disclosure by VulnCheck and NVD