CVE-2025-51472: SuperAGI · n/a
Affects SuperAGISource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubtransformeroptimus/SuperAGIpkg:github/transformeroptimus/SuperAGIOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, European organizations should first identify all instances of TransformerOptimus SuperAGI in their environments, especially version 0.0.14 or earlier if applicable. Since no official patches are currently available, organizations should implement immediate compensating controls: 1) Restrict network access to systems running SuperAGI to trusted internal networks or VPNs to reduce exposure to remote attackers. 2) Employ strict input validation and sanitization on all agent template configuration inputs before they are processed by the eval_agent_config function, ideally by disabling or replacing the use of eval() with safer parsing methods. 3) Monitor logs and system behavior for unusual activity indicative of code injection attempts. 4) Use application-layer firewalls or runtime application self-protection (RASP) tools to detect and block malicious payloads targeting configuration fields. 5) Engage with the vendor or open-source maintainers to obtain or contribute patches that remove unsafe eval() usage. 6) Implement strict role-based access controls to limit who can modify agent templates, reducing the risk of insider threats or accidental injection. 7) Conduct security reviews and code audits on AI agent configuration handling to prevent similar vulnerabilities in future versions.
Description
Code Injection in AgentTemplate.eval_agent_config in TransformerOptimus SuperAGI 0.0.14 allows remote attackers to execute arbitrary Python code via malicious values in agent template configurations such as the goal, constraints, or instruction field, which are evaluated using eval() without validation during template loading or updates.