# CVE-2026-51915: Missing authorization in n/a

> Remote authenticated attackers can read or modify other organizations' tool metadata due to missing ownership verification in the tool controller.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-cwmh-qrfg-2hgm

## What is CVE-2026-51915?

CVE-2026-51915 is a critical missing authorization vulnerability in n/a, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TransformerOptimus SuperAGI v0.0.14 is vulnerable to Incorrect Access Control in the tool controller. In affected source snapshots, get_tool and update_tool in superagi/controllers/tool.py accept a caller-supplied tool_id and fail to verify organization ownership through the associated toolkit. A remote authenticated attacker from one organization can read or modify another organization's tool metadata through /tools/get/{tool_id} and /tools/update/{tool_id}.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-51915 being exploited?

There is no known exploitation of CVE-2026-51915 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51915 is a critical missing authorization vulnerability in n/a, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-51915 in the wild and no public exploit code.

Affected product: n/a. 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-51915/ (Markdown: https://insights.sbomify.com/CVE-2026-51915/index.md)
```

## Sources

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

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