Auth bypass in Yeti-Platform Yeti
CVE-2026-92783
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.
Vulnerability class: Broken Access Control
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H.
EPSS exploit prediction
EPSS: 0.005 (43.1th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 43rd percentile — 43.1% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.005 · newest: 0.005 · change: 0.000
Affected products
Weakness classification (CWE)
References
- github.com/yeti-platform/yeti/issues/1349 (issue-tracking)
- github.com/yeti-platform/yeti (product)
- github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py (technical-description)
- github.com/yeti-platform/yeti/blob/2.5.1/core/web/apiv2/rbac.py (technical-description)
- www.vulncheck.com/advisories/yeti-through-2.11.0-missing-authorization-on-rbac-… (third-party-advisory)
Frequently asked questions
- What is CVE-2026-92783?
- CVE-2026-92783 is a high-severity vulnerability in Yeti-Platform Yeti, classified under Missing Authorization. CVSS score: 8.1/10. Published 2026-09-16.
- How severe is CVE-2026-92783?
- High severity. CVSS v3 base score is 8.1 out of 10.