{"answers":{"affected":"6 open source packages ship an affected version, including github.com/kyverno/kyverno and kyverno. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22039 exists.","fix":"Upgrade github.com/kyverno/kyverno to a fixed version for your release line: 1.15.3 or 1.16.3.","what":"CVE-2026-22039 is a critical vulnerability in kyverno, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-22039 and fix it if it is affected.\n\nWhat it is: CVE-2026-22039 is a critical vulnerability in kyverno, published on 27 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22039 exists.\n\nAffected packages and fixed versions:\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.15.3, 1.16.3\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.15.3\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.15.3\n- github.com/kyverno/kyverno (Go): affected from 1.16.0-rc.1; fixed in 1.16.3\n- github.com/kyverno/kyverno (Go): affected from 1.16.0-rc.1; fixed in 1.16.3\n- kyverno (Bitnami): affected all versions; fixed in 1.15.3, 1.16.3\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-22039/ (Markdown: https://insights.sbomify.com/CVE-2026-22039/index.md)","id":"CVE-2026-22039","markdown":"https://insights.sbomify.com/CVE-2026-22039/index.md","name":"CVE-2026-22039","record":{"aliases":["BIT-kyverno-2026-22039","CLEANSTART-2026-KS35076","GHSA-8p9x-46gm-qfx2","GO-2026-4381","MINI-2547-2gp7-7c93","MINI-38gc-3r2h-4qq2","MINI-489c-r79v-5x92","MINI-4r6c-gc9v-fm6p","MINI-5gmq-9cxc-757j","MINI-5pc3-4qrc-2gpg","MINI-63v9-cj9g-2wph","MINI-7rj9-qq3g-w42q","MINI-8wr4-xwp4-7x7q","MINI-cpr4-mhhf-5hcv","MINI-pf52-mpgh-vffc","MINI-w4hp-q29f-gp3r","MINI-wh22-f3x5-49xw"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes policy engine","requires_auth":"low_privilege","summary":"Authenticated users can escalate privileges and access cross-namespace resources by exploiting Kyverno's policy apiCall feature to bypass namespace isolation.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kyverno","vendor":"kyverno"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Kyverno is a policy engine designed for cloud native platform engineering teams. Versions prior to 1.16.3 and 1.15.3 have a critical authorization boundary bypass in namespaced Kyverno Policy apiCall. The resolved `urlPath` is executed using the Kyverno admission controller ServiceAccount, with no enforcement that the request is limited to the policy’s namespace. As a result, any authenticated user with permission to create a namespaced Policy can cause Kyverno to perform Kubernetes API requests using Kyverno’s admission controller identity, targeting any API path allowed by that ServiceAccount’s RBAC. This breaks namespace isolation by enabling cross-namespace reads (for example, ConfigMaps and, where permitted, Secrets) and allows cluster-scoped or cross-namespace writes (for example, creating ClusterPolicies) by controlling the urlPath through context variable substitution. Versions 1.16.3 and 1.15.3 contain a patch for the vulnerability.","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Kyverno Cross-Namespace Privilege Escalation via Policy apiCall","id":"CVE-2026-22039","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":6,"n_references":3,"next":{"headline":"NanoMQ 0.24.6 Use-After-Free Leading to Heap Corruption and Broker Crash","id":"CVE-2026-22040"},"packages":[{"ecosystem":"Bitnami","fixed":["1.15.3","1.16.3"],"introduced":["0","1.16.0"],"last_affected":[],"package":"kyverno","purl":"pkg:bitnami/kyverno","source":"BIT-kyverno-2026-22039"},{"ecosystem":"Go","fixed":["1.15.3","1.16.3"],"introduced":["0","1.16.0-rc.1"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":"pkg:golang/github.com/kyverno/kyverno","source":"GO-2026-4381"},{"ecosystem":"Go","fixed":["1.15.3"],"introduced":["0"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":null,"source":"GHSA-8p9x-46gm-qfx2"},{"ecosystem":"Go","fixed":["1.15.3"],"introduced":["0"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":"pkg:golang/github.com/kyverno/kyverno","source":"GHSA-8p9x-46gm-qfx2"},{"ecosystem":"Go","fixed":["1.16.3"],"introduced":["1.16.0-rc.1"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":null,"source":"GHSA-8p9x-46gm-qfx2"},{"ecosystem":"Go","fixed":["1.16.3"],"introduced":["1.16.0-rc.1"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":"pkg:golang/github.com/kyverno/kyverno","source":"GHSA-8p9x-46gm-qfx2"}],"prev":{"headline":"AutoGPT's API Keys and Secrets Logged in Plaintext in Stagehand Integration Blocks","id":"CVE-2026-22038"},"products":["kyverno"],"published":"2026-01-27","related":[{"cvss_score":9.8,"headline":"CVE-2026-4789","id":"CVE-2026-4789","kev_date_added":null,"published":"2026-03-30"},{"cvss_score":8.6,"headline":"Kyverno vulnerable to bypass of policy rules that use namespace selectors in match statements","id":"CVE-2025-46342","kev_date_added":null,"published":"2025-04-30"},{"cvss_score":8.1,"headline":"Kyverno: ServiceAccount token leaked to external servers via apiCall service URL","id":"CVE-2026-41323","kev_date_added":null,"published":"2026-04-24"},{"cvss_score":8.1,"headline":"kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token","id":"CVE-2026-40868","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":8.1,"headline":"kyverno verifyImages rule bypass possible with malicious proxy/registry","id":"CVE-2022-47633","kev_date_added":null,"published":"2022-12-23"},{"cvss_score":7.7,"headline":"Kyverno: Cross-Namespace Read Bypasses RBAC Isolation (CVE-2026-22039 Incomplete Fix)","id":"CVE-2026-41068","kev_date_added":null,"published":"2026-04-24"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-27","vendors":["kyverno"]},"summary":"Authenticated users can escalate privileges and access cross-namespace resources by exploiting Kyverno's policy apiCall feature to bypass namespace isolation.","url":"https://insights.sbomify.com/CVE-2026-22039/"}