Cross-organization key deletion via missing ownership checks
Published Apr 19, 2026 · Updated Apr 19, 2026
Improper authorization in SuperAGI 0.0.14 and earlier allows remote authenticated users to modify or delete other organizations' API keys. The delete_api_key and edit_api_key handlers retrieve records from caller-controlled key IDs after validating a JWT but never verify that the record belongs to the caller's organization. Any account with a valid JWT can target another tenant's numeric key ID, enabling key renaming, access revocation, and interruption of integrations that depend on a deleted key.
Summary
What happened
Improper authorization in SuperAGI 0.0.14 and earlier allows remote authenticated users to modify or delete other organizations' API keys. The delete_api_key and edit_api_key handlers retrieve records from caller-controlled key IDs after validating a JWT but never verify that the record belongs to the caller's organization. Any account with a valid JWT can target another tenant's numeric key ID, enabling key renaming, access revocation, and interruption of integrations that depend on a deleted key.
The record
- CVE
- CVE-2026-6583
- Published
- Apr 19, 2026
- Updated
- Apr 19, 2026
- Vendor
- SuperAGI
- Product
- SuperAGI
- Classifications
- CWE-285, CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 19, 2026CVE publishedPublication date reported by the CVE source.
- Apr 19, 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
- Cross-organization API-key IDOR proof of conceptproof of concept · demonstrated
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