Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
bentoml/Yatai
main @ 419711b
4
Fixes
0
CVEs
HIGH
Peak severity
75.0%
Coverage
Highlights
Auth Bypass: 4 prior fixes. Scrutinize any change in this area.
api-server/controllers/controllersv1/auth.go: most-fixed (1 issue). Treat as high-risk during review.
4 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Auth Bypass: Download endpoints used canUpdate (write permission) instead of canView, blocking legitimate view-only users and potentially exposing a bypass for users with any write access.
Auth Bypass: The getLoginUser function lacked any permission check for the current organization, allowing a user to resolve another user's identity without verifying they belong to or can view the org.
Auth Bypass: Component get/list operations used canOperate (write permission) instead of canView, meaning users with write access could access components beyond their view scope.