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

> Remote authenticated attackers can create or start execution records for agents owned by other organizations due to missing ownership verification.

- **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:** 5 Oct 2026
- **Also known as:** GHSA-63jh-v3gf-wqcq

## What is CVE-2026-51904?

CVE-2026-51904 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

SuperAGI up to v0.0.14 contains an improper access control vulnerability in the agent execution controller. In affected source snapshots, create_agent_execution and create_agent_run in superagi/controllers/agent_execution.py accept a caller-supplied agent_id and fail to verify that the referenced agent belongs to the authenticated user's organization. A remote authenticated attacker from one organization can create or start execution records for agents owned by another organization through /agentexecutions/add or /agentexecutions/add_run.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-51904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51904 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-51904 exists.

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-51904/ (Markdown: https://insights.sbomify.com/CVE-2026-51904/index.md)
```

## Sources

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

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