{"id":"CVE-2026-92393","title":"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\", \"…","summary":"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\", \"…","severity":"low","cvss":2,"cvssVector":"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","vendor":"Apache Software Foundation","product":"github.com/apache/yunikorn-k8shim","affected":["github.com/apache/yunikorn-k8shim < 1.10.0"],"published":"2026-10-07","updated":"2026-10-07","sourceUpdated":"2026-10-07T10:17:42.247","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-92393","references":[{"url":"https://lists.apache.org/thread.html/sfo83zlrrx9ftbox9oxcp03qox2co449","label":"security@apache.org"},{"url":"http://www.openwall.com/lists/oss-security/2026/10/07/25","label":"af854a3a-2127-422b-91ae-364da2661108"}],"tags":["nvd","cve.org"],"cvssSource":"cna","ingestedAt":"2026-10-07T10:25:12.189Z","slug":"CVE-2026-92393","body":"## Overview\n\nApache 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.\n\n\nThe 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.\n\n\n\n\nUsers are recommended to upgrade to version 1.10.0, which fixes this issue.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"sunlit","depthScore":11,"depthScoreParts":{"impact":11,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}