{"answers":{"affected":"4 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-40868 exists.","fix":"Upgrade github.com/kyverno/kyverno to 1.17.0 or later.","what":"CVE-2026-40868 is a high-severity vulnerability in kyverno, published on 21 Apr 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-40868 and fix it if it is affected.\n\nWhat it is: CVE-2026-40868 is a high-severity vulnerability in kyverno, published on 21 Apr 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-40868 exists.\n\nAffected packages and fixed versions:\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.17.0\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.17.0\n- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.17.0\n- kyverno (Bitnami): affected all versions; fixed in 1.16.4\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-40868/ (Markdown: https://insights.sbomify.com/CVE-2026-40868/index.md)","id":"CVE-2026-40868","markdown":"https://insights.sbomify.com/CVE-2026-40868/index.md","name":"CVE-2026-40868","record":{"aliases":["BIT-kyverno-2026-40868","ECHO-a7ef-0b97-6536","GHSA-q93q-v844-jrqp","GO-2026-5575","MINI-2p4q-qpv3-v7f4","MINI-6gh8-p2rc-3wxq","MINI-739j-gp4v-qjx6","MINI-73h3-hvqm-x396","MINI-92hf-6g2f-pm64","MINI-c25w-m2x5-98hv","MINI-fhq4-rpw6-7xgr","MINI-fr29-5gmv-wrpq","MINI-ghmq-rv63-vj6h","MINI-pxj5-vw53-ph3f","MINI-qvpw-g27m-p78v","MINI-qwq4-9f8j-8j3f","MINI-vv5x-c496-x2wx"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes policy engine","requires_auth":"low_privilege","summary":"Attackers can leak Kyverno service account tokens to external endpoints via policy-controlled API calls, enabling unauthorized access to cluster resources.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kyverno","vendor":"kyverno"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"}],"description":"Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to 1.16.4, kyverno’s apiCall servicecall helper implicitly injects Authorization: Bearer ... using the kyverno controller serviceaccount token when a policy does not explicitly set an Authorization header. Because context.apiCall.service.url is policy-controlled, this can send the kyverno serviceaccount token to an attacker-controlled endpoint (confused deputy). Namespaced policies are blocked from servicecall usage by the namespaced urlPath gate in pkg/engine/apicall/apiCall.go, so this report is scoped to ClusterPolicy and global context usage. This vulnerability is fixed in 1.16.4.","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 apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token","id":"CVE-2026-40868","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"Decidim amendments can be accepted or rejected by anyone","id":"CVE-2026-40869"},"packages":[{"ecosystem":"Bitnami","fixed":["1.16.4"],"introduced":["0"],"last_affected":[],"package":"kyverno","purl":"pkg:bitnami/kyverno","source":"BIT-kyverno-2026-40868"},{"ecosystem":"Go","fixed":["1.17.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":null,"source":"GHSA-q93q-v844-jrqp"},{"ecosystem":"Go","fixed":["1.17.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":"pkg:golang/github.com/kyverno/kyverno","source":"GHSA-q93q-v844-jrqp"},{"ecosystem":"Go","fixed":["1.17.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kyverno/kyverno","purl":"pkg:golang/github.com/kyverno/kyverno","source":"GO-2026-5575"}],"prev":{"headline":"Horilla: Unauthorized Helpdesk Attachment Access via Attachment ID Manipulation","id":"CVE-2026-40867"},"products":["kyverno"],"published":"2026-04-21","related":[{"cvss_score":10,"headline":"Kyverno Cross-Namespace Privilege Escalation via Policy apiCall","id":"CVE-2026-22039","kev_date_added":null,"published":"2026-01-27"},{"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 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-04-22","vendors":["kyverno"]},"summary":"Attackers can leak Kyverno service account tokens to external endpoints via policy-controlled API calls, enabling unauthorized access to cluster resources.","url":"https://insights.sbomify.com/CVE-2026-40868/"}