CVE-2026-92393

Apache YuniKorn: Admission control bypass via workload UPDATE operation

Published Oct 7, 2026 CVSS 4.0 · 2 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Apache YuniKorn 1.9.0 and earlier fail to validate user and label annotations when a workload is updated. The UPDATE operation bypasses all admission checks, allowing any authorized user to set an arbitrary user annotation or change the application ID. This can let a user run a workload in a queue that they normally are not allowed to use, potentially violating queue quotas and altering user–based quota enforcement. The flaw does not directly expose data or crash the system, but it enables unauthorized resource usage and can lead to resource exhaustion or misreporting of usage.

Affected Systems

The vulnerability affects Apache YuniKorn as distributed by the Apache Software Foundation. Versions 1.9.0 and earlier are impacted. Workloads for Kubernetes objects such as deployments, replicasets, statefulsets, daemonsets, jobs, and cronjobs are subject to the update bypass.

Risk and Exploitability

The CVSS score of 2.0 reflects a low severity vulnerability. EPSS score of 0.00452 indicates a very low exploitation probability, and the issue is not listed in CISA’s KEV catalog, indicating low reported exploitation risk. The likely attack vector is via remote or local access to the YuniKorn API, where a user who can perform UPDATE requests can leverage the bypass. Because the vulnerability is a missing authorization check, an attacker would need to be authenticated to the YuniKorn service; no privilege escalation beyond that is required.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Apache YuniKorn to version 1.10.0 or later to apply the fix that restores admission checks for UPDATE actions.
  • If an upgrade is not immediately possible, restrict UPDATE permissions in YuniKorn’s RBAC configuration so that only administrators can modify user annotations or application IDs.
  • Audit queue assignments and user quota logs for unauthorized changes, and enforce manual review of any UPDATE operations that alter labels or user information.

Generated by OpenCVE AI on October 7, 2026 at 20:06 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Apache
Apache yunikorn
Vendors & Products Apache
Apache yunikorn
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-863
Type Values Removed Values Added
Weaknesses CWE-862
Type Values Removed Values Added
Description 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.
Title Apache YuniKorn: Admission control bypass via workload UPDATE operation
References
Metrics cvssV4_0

{'score': 2, '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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Oct 7, 2026, 5:52 PM
Reserved
Sep 16, 2026, 8:16 AM
Status
Deferred
Published
Oct 7, 2026, 10:17 AM
Modified
Oct 7, 2026, 6:17 PM