# CVE-2026-92783: Yeti through 2.11.0 Missing Authorization on RBAC Relationship Deletion

> Attackers with read access can delete RBAC relationships, revoking owner grants and locking legitimate users out of objects.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA: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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-w297-93hv-q3cx

## What is CVE-2026-92783?

CVE-2026-92783 is a high-severity missing authorization vulnerability in yeti-platform yeti, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Yeti through 2.11.0 fails to validate caller permissions in the DELETE /api/v2/rbac/{id} endpoint, allowing users with read access to delete access control relationships. Attackers can revoke the owner's grant and permanently lock legitimate owners out of objects.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-92783 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92783 is a high-severity missing authorization vulnerability in yeti-platform yeti, published on 16 Sep 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-92783 exists.

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

## Sources

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

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