Queue access bypass via forged system pod label
Published Oct 7, 2026 · Updated Oct 7, 2026
Improper authorization in Apache YuniKorn 1.9.0 and earlier allows remote authenticated users to bypass pod user-annotation checks. The admission controller treats the app=yunikorn pod label as a system-pod exemption without verifying its namespace, so a forged label skips user-info validation. A user able to submit pods can supply arbitrary identity metadata, undermining queue access controls and user quota tracking.
Summary
What happened
Improper authorization in Apache YuniKorn 1.9.0 and earlier allows remote authenticated users to bypass pod user-annotation checks. The admission controller treats the app=yunikorn pod label as a system-pod exemption without verifying its namespace, so a forged label skips user-info validation. A user able to submit pods can supply arbitrary identity metadata, undermining queue access controls and user quota tracking.
The record
- CVE
- CVE-2026-97146
- Published
- Oct 7, 2026
- Updated
- Oct 7, 2026
- Vendor
- Apache Software Foundation
- Product
- Apache YuniKorn
- Classifications
- CWE-285, T1565
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2026CVE publishedPublication date reported by the CVE source.
- Oct 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started