Security Digest · Vulnerability record

CVE-2026-35002: Agno is vulnerable to Eval Injection

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().

CVSS 9.3 Critical EPSS 1.1% · p67

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 1.1%, percentile 67: FIRST’s model estimates a 1.1% chance of exploitation activity in the next 30 days, higher than 67% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes agno (PyPI) < 2.3.24, fixed in 2.3.24. Check your lockfile, including transitive dependencies.

What it is

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.

From the GitHub advisory

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.

Weakness type: CWE-95.

Product: agno (PyPI) · Assigned by: VulnCheck · Published: 2026-04-02

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIagno< 2.3.242.3.24
VendorProductAffected versions (per CVE record)
AgnoAgno< 2.3.24, cbf675521d4d2281925a051784a3b94172e56416

Severity scores

Scored byCVSSScoreVector
VulnCheck4.09.3 CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
GitHub4.09.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
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 1.15% probability of exploitation activity in the next 30 days; percentile 67.

Timeline

  • — CVE record published by VulnCheck
  • — GitHub-reviewed advisory GHSA-77rh-m34w-rv36 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. github.com github.com
  2. github.com github.com

Vulnerability records

  1. GitHub Advisory GHSA-77rh-m34w-rv36 github.com
  2. CVE.org record CVE-2026-35002 cve.org
  3. NVD entry CVE-2026-35002 nvd.nist.gov

Other references from the CVE record and advisory

  1. vulncheck.com vulncheck.com

Critical PyPI advisories · Today’s Security Digest