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.
Security readout for executives and security teams
Plain-English summary
Agno before 2.3.24 can treat attacker-controlled type information as Python code. A successful attack could let an unauthenticated remote actor control the affected Agno process and compromise its data, integrity, and availability.
Executive priority
Treat this as an immediate patching priority for exposed or externally influenced Agno services. Complete rapid inventory and upgrade to 2.3.24 or later. The technical impact is critical, although the supplied evidence does not show active exploitation.
Technical view
The model execution component passes a FunctionCall field_type value to eval(). An attacker able to influence that value can inject Python expressions, producing arbitrary code execution. The CVSS 4.0 score is 9.3, with network access, low complexity, no privileges, and no user interaction required.
Likely exposure
Exposure exists where Agno versions before 2.3.24 process FunctionCall data that an external or less-trusted party can influence. Risk is greatest for network-accessible model or agent services. The bundle does not establish that every Agno deployment exposes this data path.
Exploitation context
The provided bundle does not establish active exploitation, and the CVE is not listed as KEV. The CVSS vector nevertheless describes a remotely reachable, unauthenticated, low-complexity path with complete impact to the vulnerable system when the affected data flow is exposed.
Researcher notes
The issue maps to CWE-95 and is addressed by release 2.3.24 and commit cbf675521d4d2281925a051784a3b94172e56416. Reachability depends on whether an attacker can influence field_type within FunctionCall. The bundle provides no confirmed exploitation evidence or deployment-specific indicators of compromise.
Mitigation direction
Upgrade Agno to version 2.3.24 or later following the vendor release guidance.
Prioritize upgrades for network-accessible services processing externally influenced FunctionCall data.
Until upgraded, prevent untrusted inputs from influencing field_type and reduce access to affected services.
Review the vendor patch and advisory for deployment-specific remediation guidance.
Validation and detection
Inventory deployed and transitive Agno versions; identify every instance earlier than 2.3.24.
Trace whether external or less-trusted data can influence FunctionCall field_type values.
Confirm upgraded environments report Agno 2.3.24 or later.
Review relevant logs for unusual field_type values or unexpected Python execution behavior.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
4Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-95 · source CWE mapping
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.