CVE-2026-97146: Apache YuniKorn: Admission control bypass via system label forgery
Apache YuniKorn 1.9.0 and earlier allows bypassing the check for the user annotation by setting a secondary label on the pod. If the pod has the label 'app=yunikorn' the checks limiting the user annotation content are not run. The label is used to identify the YuniKorn application itself in the deployments.
The bypass allows any user to specify an arbitrary user info annotation. The arbitrary user information 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
Which deployments require remediation?
Apache YuniKorn 1.9.0 and earlier are affected. Upgrading to version 1.10.0 is recommended because it fixes the issue.
What conditions trigger the bypass?
A pod with the label app=yunikorn bypasses the checks that limit the contents of the user annotation. An attacker can then provide arbitrary user information in that annotation.
What is the operational impact of forged user information?
Forged user information may allow an application to access a queue the user would not normally be permitted to use. It can also affect queue quota usage and bypass user-based quota tracking, including when the application remains in the correct queue.