# CVE-2026-6583: TransformerOptimus SuperAGI API Key Management Endpoint api_key.py edit_api_key authorization

> Attackers can bypass authorization to modify or delete API keys in SuperAGI, potentially compromising account security and data integrity.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-fqhh-6rmf-f4vh

## What is CVE-2026-6583?

CVE-2026-6583 is a medium-severity missing authorization vulnerability in TransformerOptimus SuperAGI, published on 19 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in TransformerOptimus SuperAGI up to 0.0.14. This affects the function delete_api_key/edit_api_key of the file superagi/controllers/api_key.py of the component API Key Management Endpoint. The manipulation leads to authorization bypass. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-6583?


## How do I fix CVE-2026-6583?

No fix has been published for CVE-2026-6583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6583 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6583 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6583 and fix it if it is affected.

What it is: CVE-2026-6583 is a medium-severity missing authorization vulnerability in TransformerOptimus SuperAGI, published on 19 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6583 exists.

Affected product: TransformerOptimus SuperAGI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6583/ (Markdown: https://insights.sbomify.com/CVE-2026-6583/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6583
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6583
- OSV: https://osv.dev/vulnerability/CVE-2026-6583

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6583/
Summaries are generated and may contain mistakes; the official description above is the record.