CVE-2026-92783: Missing Authorization in yeti-platform yeti
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.
AI Analysis
Technical Summary
CVE-2026-92783 describes a missing authorization vulnerability in the yeti-platform (yeti) through version 2.11.0. The DELETE /api/v2/rbac/{id} API endpoint does not properly validate whether the caller has sufficient permissions to delete role-based access control (RBAC) relationships. As a result, users with read-only access can delete access control grants, including those of legitimate owners, which can lead to permanent loss of access to objects for those owners.
Potential Impact
An attacker with read access can delete RBAC relationships, including the owner's grant, causing legitimate owners to lose access permanently. This can disrupt normal operations and potentially cause denial of access to critical resources managed by the platform.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict read access to trusted users only and monitor for suspicious deletion activity on RBAC relationships.
CVE-2026-92783: Missing Authorization in yeti-platform yeti
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.
CVSS v4.0
Score 7.2high
Affected software
yeti-platform
yeti
pkg:github/yeti-platform/yetiRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-92783 describes a missing authorization vulnerability in the yeti-platform (yeti) through version 2.11.0. The DELETE /api/v2/rbac/{id} API endpoint does not properly validate whether the caller has sufficient permissions to delete role-based access control (RBAC) relationships. As a result, users with read-only access can delete access control grants, including those of legitimate owners, which can lead to permanent loss of access to objects for those owners.
Potential Impact
An attacker with read access can delete RBAC relationships, including the owner's grant, causing legitimate owners to lose access permanently. This can disrupt normal operations and potentially cause denial of access to critical resources managed by the platform.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict read access to trusted users only and monitor for suspicious deletion activity on RBAC relationships.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-09-16T19:22:54.542Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aab006155bf5e2cf5231e04
Added to database: 09/16/2026, 20:47:29 UTC
Last enriched: 09/16/2026, 21:48:38 UTC
Last updated: 09/17/2026, 02:02:55 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.