{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-92393 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-92393 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-92393 is a low-severity missing authorization vulnerability in Apache YuniKorn, published on 7 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-92393 and fix it if it is affected.\n\nWhat it is: CVE-2026-92393 is a low-severity missing authorization vulnerability in Apache YuniKorn, published on 7 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-92393 in the wild and no public exploit code.\n\nAffected product: Apache YuniKorn. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-92393/ (Markdown: https://insights.sbomify.com/CVE-2026-92393/index.md)","id":"CVE-2026-92393","markdown":"https://insights.sbomify.com/CVE-2026-92393/index.md","name":"CVE-2026-92393","record":{"aliases":["GHSA-q2pg-9xr3-7r4g"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes resource scheduler","requires_auth":"high_privilege","summary":"Attackers can bypass admission control checks during workload updates to access unauthorized queues and evade quota enforcement in Apache YuniKorn.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.\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\nUsers are recommended to upgrade to version 1.10.0, which fixes this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Apache YuniKorn: Admission control bypass via workload UPDATE operation","id":"CVE-2026-92393","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"@fastify/proxy-addr vulnerable to IP spoofing via IPv4-mapped IPv6 trust subnet","id":"CVE-2026-92395"},"packages":[],"prev":{"headline":"HTTP/2 upload Use-After-Free","id":"CVE-2026-92392"},"products":["Apache YuniKorn"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass admission control checks during workload updates to access unauthorized queues and evade quota enforcement in Apache YuniKorn.","url":"https://insights.sbomify.com/CVE-2026-92393/"}