Live › vulnerability › CVE-2026-51903
SuperAGI v0.0.14 lets a logged-in user from one organization fetch the latest execution and agent metadata of another organization's project by supplying that project's ID to an API endpoint. The attacker gets exposure of another tenant's agent activity data, not code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 18:26 UTC. All times on this page are UTC.
Teams that run SuperAGI with multiple organizations or tenants sharing one instance are the ones exposed, since the flaw is cross-organization access. A single-tenant deployment where every user belongs to the same organization is less exposed. The sources do not state which fixed version exists.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| SuperAGI | github | <= 0.0.14 | – |
0.0.14, for example in the deployed image tag or repository release.superagi/controllers/agent_execution.py for the get_agent_by_latest_execution handler and whether it verifies the project belongs to the caller's organization./agentexecutions/get/latest/agent/project/{project_id} returns data for a project ID outside your organization's tenant (unknown if sources give a test procedure).No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
SuperAGI v0.0.14 contains an improper access control vulnerability in get_agent_by_latest_execution in superagi/controllers/agent_execution.py. A remote authenticated attacker from one organization can retrieve latest execution and agent metadata for another organization's project through /agentexecutions/get/latest/agent/project/{project_id} by supplying a victim project_id.
This page as .md · .json · in your agent: get_signal("CVE-2026-51903")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.