---
id: CVE-2026-97146
title: "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"
summary: "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 …"
severity: medium
cvss: 4.8
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/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:43.693'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-97146'
references:
  - url: 'https://lists.apache.org/thread.html/nds5ct9xzlo4fp0jfr1rx6jxm03g0jro'
    label: security@apache.org
  - url: 'http://www.openwall.com/lists/oss-security/2026/10/07/26'
    label: af854a3a-2127-422b-91ae-364da2661108
tags:
  - nvd
  - cve.org
cvssSource: cna
ingestedAt: '2026-10-07T10:25:12.190Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.