Skip to main content

Agno CVE-2026-37003

| EUVDEUVD-2026-67272 CRITICAL
Code Injection (CWE-94)
2026-08-27 mitre GHSA-g3w9-2xgv-r24v
9.8
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify Agno agent ingesting external content
  2. Delivery
    Plant malicious instructions in web page/document
  3. Exploit
    Agent processes content and emits tool call
  4. Execution
    PythonTools/ShellTools passes args to exec/subprocess
  5. Impact
    Arbitrary OS command execution on host

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the target Agno deployment has the PythonTools and/or ShellTools components enabled and that the agent processes attacker-influenceable content (e.g., a web page or document the attacker can plant instructions in). Given those, per the CVSS vector no authentication or user interaction is needed and the vector is network-reachable. The key LIMITING factors are configuration-dependent: if the code-execution tools are not enabled, or the agent never ingests untrusted content, the vulnerability is not reachable - so this is not exploitable against a default agent that lacks these tools, despite the 9.8/PR:N rating.

Impact

The signals conflict and should be weighed carefully. CVSS 3.1 (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H = 9.8) treats this as trivial remote unauthenticated full compromise, but that rating assumes the worst-case deployment. Real-world exploitability is gated by two conditions the CVSS score does not capture: the application must have enabled the code-execution tools (PythonTools/ShellTools), and it must route attacker-influenced content through the agent. EPSS is low (0.60%, 46th percentile) and there is no KEV listing and no public exploit identified, which is consistent with a serious-but-not-yet-widely-weaponized issue rather than mass exploitation. SSVC framing: technical impact is total, but 'automatable' is questionable because success depends on non-default, high-risk tool configuration. Net: genuinely critical for any deployment that exposes PythonTools/ShellTools to untrusted content, and largely inapplicable to deployments that do not enable those tools - so prioritize based on your own configuration rather than the raw 9.8.

Exploit ScenarioDerived

An organization runs an Agno agent with PythonTools/ShellTools enabled to summarize web pages on demand. An attacker publishes a page containing hidden instructions that coerce the model into calling ShellTools with an attacker-chosen command; when the agent fetches and processes the page, the command executes on the host server. No public exploit code is identified, but the technique (indirect prompt injection into a code-execution tool) is well understood and the attack is network-reachable and unauthenticated.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.6% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 01, 2026

Remote code execution in Agno (the Python AI-agent framework) up to and including 2.5.8 lets attackers run arbitrary code and OS commands on the host by way of prompt injection. The PythonTools and ShellTools components feed LLM-generated arguments straight into exec(), runpy.run_path(), and subprocess.run() without sanitization, so an attacker who plants malicious instructions in any content the agent ingests (a web page, a document) can hijack execution. CVSS is rated 9.8 and the CVSS vector marks it unauthenticated/network, but no public exploit is identified at time of analysis and EPSS is low at 0.60% (46th percentile).

RemediationAI

No vendor-released patched version is identified at time of analysis, so upgrade to a fixed Agno release as soon as one is published beyond 2.5.8 and monitor http://agno.com and the NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-37003) for the fixed version. As compensating controls until then: disable the PythonTools and ShellTools tools in agent configurations that process any untrusted input (this removes the code-execution sink but obviously removes those capabilities from the agent); if the tools are required, run the agent in a strongly sandboxed, network-restricted, least-privilege container or microVM so that code execution cannot reach production data or lateral targets (trade-off: added operational complexity and latency); and restrict which content sources the agent is allowed to ingest, avoiding fetching arbitrary web pages or user-supplied documents through code-capable agents (trade-off: reduced automation scope). Do not rely on prompt-level guardrails alone, since the root cause is unsanitized arguments reaching execution sinks.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Agno is an open-source Python framework for building LLM agents (previously known as Phidata) that ships optional 'tools' an agent can call during reasoning. Two of those tools - PythonTools and ShellTools - are designed to execute code and shell commands, and the flaw is that the arguments to those tools come from untrusted LLM output that is itself steerable by attacker-supplied content. This is a textbook CWE-94 (Improper Control of Generation of Code / code injection): the dangerous sinks exec(), runpy.run_path(), and subprocess.run() receive unsanitized strings, so anything that influences the model's tool-call arguments influences what code runs. The CPE string cpe:2.3:a:n/a:n/a is a placeholder and does not identify the real product; the affected component is the Agno library itself.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Network-reachable and unauthenticated with total impact, but AC:H because it depends on the non-default configuration of enabling code-execution tools and routing untrusted content through the agent.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Sep 01, 2026 - 20:22 NVD
9.8 (CRITICAL)
CVE Published
Aug 27, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 27, 2026 - 00:00 cve.org
CRITICAL 9.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Agno (Python AI-agent framework) through version 2.5.8 contains a critical remote code execution vulnerability that can be triggered when the platform processes any untrusted content, including web pages, documents, or user inputs. Organizations relying on Agno for automation face risk of complete system compromise if an attacker injects malicious instructions into content the agent processes. No vendor patch is available at present, and the vulnerability is config-dependent but carries broad risk for organizations with PythonTools or ShellTools enabled.

Business Impact: High
Compensating Controls

Disable PythonTools and ShellTools on all deployments unless absolutely required for business operations; implement input validation and content-source restrictions (trusted data only); deploy network segmentation to isolate affected systems from sensitive infrastructure; enable runtime monitoring for unexpected subprocess execution and file system changes.

Threat Intelligence Overview

EPSS Score
0.6%
Top 54% exploitable
Prevalence
Medium
growing open-source Python AI-agent framework, moderate but not ubiquitous adoption
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.6%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy