Cross-tenant agent control via unchecked agent ID
Published Apr 20, 2026 · Updated Apr 20, 2026
Improper authorization in SuperAGI 0.0.14 and earlier allows remote authenticated users to access or disrupt other organizations’ agents. The delete_agent, stop_schedule, and get_schedule_data handlers trust a supplied agent_id after authentication without checking that the agent belongs to the caller’s organization. A low-privileged account and another organization’s agent ID are required; successful requests expose schedule configuration, stop schedules and executions, or soft-delete the agent.
Summary
What happened
Improper authorization in SuperAGI 0.0.14 and earlier allows remote authenticated users to access or disrupt other organizations’ agents. The delete_agent, stop_schedule, and get_schedule_data handlers trust a supplied agent_id after authentication without checking that the agent belongs to the caller’s organization. A low-privileged account and another organization’s agent ID are required; successful requests expose schedule configuration, stop schedules and executions, or soft-delete the agent.
The record
- CVE
- CVE-2026-6613
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- SuperAGI
- Product
- SuperAGI
- Classifications
- CWE-639, CWE-285, T1489
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.1
- Affected versionversion=0.0.10
- Affected versionversion=0.0.11
- Affected versionversion=0.0.12
- Affected versionversion=0.0.13
- Affected versionversion=0.0.14
- Affected versionversion=0.0.2
- Affected versionversion=0.0.3
- Affected versionversion=0.0.4
- Affected versionversion=0.0.5
- Affected versionversion=0.0.6
- Affected versionversion=0.0.7
- Affected versionversion=0.0.8
- Affected versionversion=0.0.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- IDOR in Agent Management proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo