CVE-2026-40868
Kyverno ≤ 1.16.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-40868 is a high-severity Insecure Storage of Sensitive Information (CWE-922) vulnerability in Kyverno Kyverno. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-40868 is a vulnerability in Kyverno, a policy engine for cloud native platform engineering teams. In versions prior to 1.16.4, the apiCall servicecall helper implicitly injects an Authorization: Bearer header using the Kyverno controller serviceaccount token when a policy does not explicitly set one. Since the context.apiCall.service.url is controlled by the policy, this allows the token to be sent to an attacker-controlled endpoint in a confused deputy scenario. The issue is scoped to ClusterPolicy and global context usage, as namespaced policies are blocked from servicecall by a gate in pkg/engine/apicall/apiCall.go.
An attacker with low privileges (PR:L) in a Kubernetes cluster can exploit this by creating or modifying a ClusterPolicy that invokes the servicecall helper with a malicious URL. This causes Kyverno to authenticate requests to the attacker's endpoint using its highly privileged serviceaccount token, enabling theft of the token for further privilege escalation, such as accessing cluster resources. The vulnerability has a CVSS score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) and is associated with CWE-922 (Insecure Storage of Sensitive Information).
The Kyverno security advisory at GHSA-q93q-v844-jrqp states that the vulnerability is fixed in version 1.16.4. Security practitioners should upgrade to 1.16.4 or later to mitigate the issue.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-24237
Vulnerability Data
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.…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Enforces approved authorizations for logical access to stored information, directly stopping unauthorized read/write.
Requires protection of confidentiality/integrity for information at rest, directly addressing insecure storage.
Limits privileges so only authorized accesses to sensitive stored data are permitted.
Associates security attributes with information to support proper access decisions on storage.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure reuse and disposal procedures, including cryptographic wiping and physical destruction, stop the insecure storage of sensitive data on media that may later be accessed by unauthorized actors.
Mandating secure disposal techniques stops the insecure retention of sensitive information on storage media that leaves organizational control.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows Server 2016 (2 rules)
- V-224973 The Active Directory Domain Controllers Organizational Unit (OU) object must have the proper access control permissions. prevents CWE-922
- V-224974 Domain-created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-922
Windows Server 2019 (1 rule)
- V-205743 Windows Server 2019 organization created Active Directory Organizational Unit (OU) objects must have proper access control permissions. prevents CWE-922