Live › vulnerability › CVE-2026-51905
SuperAGI v0.0.14 has an endpoint that returns an agent's execution configuration when given an agent ID and execution ID, without checking that the requester belongs to the owning organization. A logged-in user from one organization can read another organization's agent execution configuration.
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.
Self-hosted SuperAGI deployments (v0.0.14 and earlier) that serve more than one organization. Any logged-in user can read another organization's agent execution configuration by guessing or learning the agent ID and execution ID. Single-organization installs where every user is trusted can mostly skip it.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| SuperAGI | github | <= 0.0.14 | – |
0.0.14 or earlier? Check superagi/controllers/agent_execution_config.py (line ~24) for an organization ownership check in get_agent_execution_configurationv0.0.14 is the latest GitHub release and the report (issue #1559) is still openEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
TransformerOptimus SuperAGI v0.0.14 is vulnerable to Incorrect Access Control in get_agent_execution_configuration in superagi/controllers/agent_execution_config.py. A remote authenticated attacker from one organization can read another organization's agent execution configuration by supplying the victim agent_id and agent_execution_id to /agent_executions_configs/details/agent_id/{agent_id}/agent_execution_id/{agent_execution_id}. The endpoint lacks an organization ownership check on the selected agent and execution.
This page as .md · .json · in your agent: get_signal("CVE-2026-51905")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.