Vulnerability 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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Kyverno | Kyverno | < 1.16.4 |
Related Weaknesses (CWE)
References
- https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqpExploitMitigationVendor Advisory
- https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqpExploitMitigationVendor Advisory
FAQ
What is CVE-2026-40868?
CVE-2026-40868 is a vulnerability with a CVSS score of 8.1 (HIGH). 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 co...
How severe is CVE-2026-40868?
CVE-2026-40868 has been rated HIGH with a CVSS base score of 8.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-40868?
Check the references section above for vendor advisories and patch information. Affected products include: Kyverno Kyverno.