Agno is vulnerable to Eval Injection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-35002: 0.86% estimated exploitation activity in the next 30 days; percentile 58.46 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 fieldtype parameter passed to eval(). Attackers can influence the fieldtype value in a FunctionCall to achieve remote code execution.

Published by the source

2 Apr 2026, 15:31 UTC

Last modified by the source

29 Jun 2026, 12:26 UTC

Source last checked

27 Oct 2026, 14:30 UTC

1. Revision 5 · withdrawn · 27 Oct 2026

   Withdrawn upstream: ghsa record GHSA-77rh-m34w-rv36

2. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-77rh-m34w-rv36

3. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-77rh-m34w-rv36

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-77rh-m34w-rv36

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35002

Advisory: Agno is vulnerable to Eval Injection
IDs: CVE-2026-35002, GHSA-77rh-m34w-rv36
Record: https://patchnext.com/advisories/cve-2026-35002 (revision 5, source checked 27 Oct 2026, 14:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: agno 2.3.24. A vendor fix does not mean a deployment is fixed.
Status: WITHDRAWN upstream. Do not act on this record without new evidence.

## Affected components
- PyPI agno: affected < 2.3.24; fixed in 2.3.24

## Suggested inspection (read-only)
- `python -m pip show agno`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on agno.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-77rh-m34w-rv36 (GitHub-reviewed advisory GHSA-77rh-m34w-rv36 lists affected ranges: PyPI agno >=0 <2.3.24)
- Verified: https://osv.dev/vulnerability/GHSA-77rh-m34w-rv36 (OSV record GHSA-77rh-m34w-rv36 lists affected ranges: PyPI agno >=0 <2.3.24 (fixed))
- Verified: https://github.com/advisories/GHSA-77rh-m34w-rv36 (ghsa record GHSA-77rh-m34w-rv36 is marked withdrawn upstream (as of 2026-10-27T13:30:35Z).)

Commands are suggestions: review each one before running it.