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

> Authenticated users can modify or delete agents in other organizations' projects due to missing ownership checks on API endpoints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-q43w-q4wm-h8j4

## What is CVE-2026-51899?

CVE-2026-51899 is a medium-severity missing authorization vulnerability in n/a, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In SuperAGI v0.0.14 and prior, controller endpoints (/api/agents/create, /api/agents/schedule, /api/agents/delete, /api/agents/edit_schedule, /api/agents/stop_schedule) allow authenticated users from one organization to create, schedule, edit, stop, and delete agents belonging to a different organization's project. The endpoints accept a project_id parameter but do not verify that the project belongs to the authenticated user's organization.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-51899 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-51899 is a medium-severity missing authorization vulnerability in n/a, published on 2 Oct 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-51899 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-51899/ (Markdown: https://insights.sbomify.com/CVE-2026-51899/index.md)
```

## Sources

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

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