CVE-2026-51903: SuperAGI v0.0.14 contains an improper access control vulnerability in get_agent_by_latest_execution
Affects SuperAGISource GCVE Database
Not known to be exploited.
Data as of 29 Oct 2026, 19:02 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
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
Users should monitor the vendor's advisories for updates and apply any forthcoming patches promptly. Until a fix is released, restrict access to the affected API endpoint to trusted users and consider additional access control measures to prevent unauthorized project ID enumeration or access.
Description
SuperAGI version 0.0.14 has an improper access control vulnerability in the get_agent_by_latest_execution function. This flaw allows a remote authenticated attacker from one organization to access the latest execution and agent metadata of another organization's project by providing the victim's project ID via a specific API endpoint.