Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
2.0
CVE-2026-92393: Apache YuniKorn allows queue bypass on workload update
CVE-2026-92393 · published 11 days ago
Summary
In versions of Apache YuniKorn up to 1.9.0, a user can change a workload's settings without the system checking who they are or what labels are attached. This can let a user move a job into a queue they shouldn't use, possibly affecting resource limits and quota tracking. Updating to version 1.10.0 fixes the problem.
What to do
- Update apache software foundation apache yunikorn to version 1.10.0 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| apache software foundation | apache yunikorn | < 1.10.0 |
Original advisory text
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.
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.
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Severity
2.0
Low
Type
CWE-863Incorrect Authorization
Timeline
Published7 Oct 2026
Updated15 Oct 2026
First seen7 Oct 2026
Track software like this
Free during beta