CVE-2026-92393: Apache YuniKorn: Admission control bypass via workload UPDATE operation
Apache YuniKorn 1.9.0 and earlier does not implement label and user annotation checks for workload UPDATE action bypassing all checks. Workloads in YuniKorn are defined as the following Kubernetes objects: "deployments", "replicasets", "statefulsets", "daemonsets", "jobs", "cronjobs". The CREATE action correctly enforces the checks for all object types.
The bypass allows any user to specify an arbitrary user info annotation. The same bypass also allows changing the application ID for the workload. The combination of the two applied in one UPDATE could allow access to a queue that the user normally would not have access to. Quota usage for the queue might be impacted if the application runs in the incorrect queue. User based quota enforcement is also based on the user annotation. User quota tracking could be side stepped even if the application runs in the correct queue.
Users are recommended to upgrade to version 1.10.0, which fixes this issue.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache YuniKornto a version that resolves this vulnerability.Fixed in 1.10.0
Event History
Frequently Asked Questions
What exploitation prerequisites are reflected in the CVSS vector?
The vector indicates network-reachable exploitation with low attack complexity, but it also requires high privileges, user interaction, and an additional attack requirement. The supplied data does not identify the specific additional requirement.
What security impact is assessed by the CVSS vector?
The vector assesses low impact to integrity and no impact to confidentiality or availability. It also indicates no impact to subsequent systems.