CVE-2026-92783
Yeti through 2.11.0 fails to validate caller permissions in the …
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 now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/yeti-platform/yeti
- github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py#L110-L116
- github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py#L52-L53
- github.com/yeti-platform/yeti/issues/1349
- www.vulncheck.com/advisories/yeti-through-2.11.0-missing-authorization-on-rbac-relationshi
- nvd.nist.gov/vuln/detail/CVE-2026-92783
- cve.org/CVERecord?id=CVE-2026-92783
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.