Cpe:2.3:a:transformeroptimus:superagi:0.0.14:*:*:*:*:*:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3atransformeroptimussuperagi0.0.14/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioFri, 30 Oct 2026 19:38:40 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgTransformerOptimus SuperAGI: Incorrect access control in get_agent_execution (CVE-2026-51905)https://feed.craftedsignal.io/briefs/2026-10-superagi-access-control/Fri, 30 Oct 2026 19:38:40 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-superagi-access-control/SuperAGI version 0.0.14 contains an incorrect access control vulnerability allowing remote authenticated attackers to bypass organization isolation and access unauthorized agent execution configurations.TransformerOptimus SuperAGI version 0.0.14 is affected by an incorrect access control vulnerability in the get_agent_execution_configuration controller, specifically within superagi/controllers/agent_execution_config.py. The vulnerability enables an authenticated attacker to access sensitive agent execution configurations of other organizations by supplying arbitrary agent_id and agent_execution_id parameters to the /agent_executions_configs/details/agent_id/{agent_id}/agent_execution_id/{agent_execution_id} endpoint. The application fails to verify organizational ownership before returning the requested data.

Impact

Successful exploitation allows a remote authenticated attacker to retrieve sensitive agent execution configurations belonging to other organizations, potentially leading to unauthorized information disclosure of proprietary workflows or agent logic.

Recommendation

  • Inventory all deployments of SuperAGI v0.0.14.
  • Implement strict ingress filtering or WAF rules to restrict access to the /agent_executions_configs/details/ endpoint if immediate patching is not possible.
  • Monitor application logs for abnormal patterns of agent_id or agent_execution_id traversal where a single user context attempts to access disparate IDs.
]]>highadvisory