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.
References
| Link | Resource |
|---|---|
| https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp | Exploit Mitigation Vendor Advisory |
| https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp | Exploit Mitigation Vendor Advisory |
Configurations
History
No history.
Information
Published : 2026-04-21 19:16
Updated : 2026-06-17 10:45
NVD link : CVE-2026-40868
Mitre link : CVE-2026-40868
CVE.ORG link : CVE-2026-40868
JSON object : View
Products Affected
kyverno
- kyverno
CWE
CWE-922
Insecure Storage of Sensitive Information
