CVE-2026-92393: Apache YuniKorn: Admission control bypass via workload UPDATE operation
Apache YuniKorn before 1.10.0 skips admission checks when workloads are updated, rated CVSS 2.0.
22
CVE-2026-92393
Workload UPDATE admission bypass in Apache YuniKorn
- CVSS 4.0
- 2.0 low
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Apache YuniKorn 1.9.0 and earlier skips label and user-annotation checks on UPDATE of Kubernetes workloads (deployments, replicasets, statefulsets, daemonsets, jobs, and cronjobs), while the same checks are enforced on CREATE. A user who can update those objects can set an arbitrary user-info annotation and change the application ID. Doing both in one update can place the workload on a queue the user should not access, distort that queue's quota, and bypass user-based quota tracking even when the queue itself is correct. The issue is fixed in 1.10.0. It is not in CISA KEV and no public proof-of-concept is known.
What to do: Upgrade Apache YuniKorn to 1.10.0 or later. Until then, restrict who can UPDATE deployments, replicasets, statefulsets, daemonsets, jobs, and cronjobs, and review recent workload updates for unexpected user-info annotations, application IDs, or queue placement that would have failed on create.
| Product | Affected |
|---|---|
| Apache YuniKorn | 1.9.0 and earlier |
Estimated exposure
nicheNo basis for an estimate.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
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.
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X