CVE-2026-37003: Agno up to and including 2.5.8 is vulnerable to Remote Code Execution (RCE) via prompt injection.
Agno up to and including 2.5.8 is vulnerable to Remote Code Execution (RCE) via prompt injection. The PythonTools and ShellTools components pass unsanitized, LLM-generated arguments directly to execution sinks including exec(), runpy.run_path(), and subprocess.run(). An unauthenticated attacker can exploit this by embedding malicious instructions in content processed by the agent (such as web pages or documents), allowing for arbitrary code and OS command execution on the host server.
Security readout for executives and security teams
Plain-English summary
Agno agents through version 2.5.8 may execute attacker-controlled code when malicious instructions are hidden in processed web pages or documents. If vulnerable execution tools are enabled, compromise could expose data, alter systems, or interrupt services without authentication or user interaction.
Executive priority
Treat internet-facing or untrusted-content-processing deployments as an immediate priority. Quickly identify affected versions and enabled execution tools, reduce exposure, and seek confirmed vendor remediation. Prioritize credential rotation and incident review where unexpected execution is detected. Lower urgency only after confirming the vulnerable tools are absent or strongly isolated.
Technical view
PythonTools and ShellTools reportedly pass unsanitized LLM-generated arguments into exec(), runpy.run_path(), and subprocess.run(). Indirect prompt injection can therefore cross the boundary from untrusted content to Python or operating-system command execution on the Agno host. The assigned CVSS 3.1 score is 9.8 under CWE-94.
Likely exposure
Highest risk applies to Agno deployments through 2.5.8 that enable PythonTools or ShellTools and allow agents to process attacker-influenced web pages, documents, or similar content. The supplied record does not identify CPEs or clarify default configurations, deployment prevalence, or whether tool access is sandboxed.
Exploitation context
The described attack is remote, unauthenticated, low complexity, and requires no user interaction. It relies on malicious instructions reaching an agent through processed content. The supplied bundle reports no CISA KEV listing and provides no evidence of active exploitation, public exploit code, or observed campaigns.
Researcher notes
The narrative explicitly identifies Agno through 2.5.8, but the structured affected-product entry contains only “n/a” and no CPEs. No fixed version, vendor advisory, patch, or exploitation evidence is supplied. Assessment of precise exposure therefore depends on local tool configuration and data flows; mitigation recommendations beyond checking vendor guidance are risk-reduction inferences from the described execution path.
Mitigation direction
Check current Agno vendor guidance for a confirmed fixed release or official mitigation.
Disable PythonTools and ShellTools where agents process untrusted or attacker-influenced content.
Restrict agent execution privileges, filesystem access, credentials, and network reach.
Isolate affected agents from sensitive production systems until remediation is confirmed.
Review processed content and host telemetry for signs of unexpected execution.
Validation and detection
Inventory Agno deployments and confirm installed versions.
Identify agents configured with PythonTools or ShellTools.
Map whether those agents ingest public web pages, documents, or other untrusted content.
Verify execution tools are disabled, isolated, or restricted pending vendor guidance.
Review logs for unexpected Python execution, subprocess activity, file changes, or outbound connections.
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-94: 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
2Source 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.