MediumGHSA-756x-m4mj-q96cCVE-2025-24784GO-2025-3435

Kubewarden-Controller information leak via AdmissionPolicyGroup Resource

Published 30 Jan 2025 · Updated 5 Feb 2025

Is your project on an affected github.com/kubewarden/kubewarden-controller?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
>=1.17.0 <1.21.0
Fixed in
1.21.0
Update to the fixed version for your release line, for example:go get github.com/kubewarden/kubewarden-controller@v1.21.0

Details

Impact

The policy group feature, added to by the 1.17.0 release, introduced two new types of CRD: ClusterAdmissionPolicyGroup and AdmissionPolicyGroup. The former is cluster wide, while the latter is namespaced.

By being namespaced, the AdmissionPolicyGroup has a well constrained impact on cluster resources. Hence, it’s considered safe to allow non-admin users to create and manage these resources in the namespaces they own. Kubewarden policies can be allowed to query the Kubernetes API at evaluation time; these types of policies are called “context aware“. Context aware policies can perform list and get operations against a Kubernetes cluster. The queries are done using the ServiceAccount of the Policy Server instance that hosts the policy. That means that access to the cluster is determined by the RBAC rules that apply to that ServiceAccount. The AdmissionPolicyGroup CRD allowed the deployment of context aware policies. This could allow an attacker to obtain information about resources that are out of their reach, by leveraging a higher access to the cluster granted to the ServiceAccount token used to run the policy.

The impact of this vulnerability depends on the privileges that have been granted to the ServiceAccount used to run the Policy Server and assumes that users are using the recommended best practices of keeping the Policy Server's ServiceAccount least privileged. By default, the Kubewarden helm chart grants access to the following resources (cluster wide) only: Namespace, Pod, Deployment and Ingress.

Patches

Starting from the 1.21.0 release, the AdmissionPolicyGroup CRD does not allow the definition of context aware policies. No modifications are needed neither for performing the upgrade nor afterwards.

Workarounds

On clusters running Kubewarden < 1.21.0, the following Kubewarden policy can be applied to prevent the creation of AdmissionPolicyGroup resources that have access to Kubernetes resources:

apiVersion: policies.kubewarden.io/v1
kind: ClusterAdmissionPolicy
metadata:
  name: "deny-admission-policy-groups-with-context-resources"
spec:
  module: registry://ghcr.io/kubewarden/policies/cel-policy:latest
  settings:
    variables:
      - name: hasContextAwareResources
        expression: "object.spec.policies.exists(p, has(object.spec.policies[p].contextAwareResources))"
      - name: isPendingDeletion
        expression: "has(object.metadata.deletionTimestamp)"
    validations:
      - expression: "!variables.hasContextAwareResources || variables.isPendingDeletion"
        message: "AdmissionPolicyGroup has contextAwareResources defined"
  rules:
    - apiGroups: ["policies.kubewarden.io"]
      apiVersions: ["v1"]
      operations: ["CREATE", "UPDATE"]
      resources: ["admissionpolicygroups"]
  mutating: false
  backgroundAudit: true

Once the policy is applied, the Kubewarden Audit Scanner can be used to identify the AdmissionPolicyGroup policies that are violating this policy.

For more information

If you have any questions or comments about this advisory you can contact the Kubewarden team using the procedures described under the “security disclosure“ guidelines of the Kubewarden project.

Is GHSA-756x-m4mj-q96c in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/kubewarden/kubewarden-controller, and gives you the command that fixes it.

More advisories for github.com/kubewarden/kubewarden-controller

  • LowCVE-2026-42541Kubewarden vulnerable to RBAC Reconnaissance via unchecked can_i host capability call in github.com/kubewarden/kubewarden-controller · 25 Jun 2026
  • MediumCVE-2026-42541Kubewarden vulnerable to RBAC Reconnaissance via unchecked can_i host capability call · 5 May 2026
  • LowCVE-2026-29773Kubewarden: Cross-namespace data exfiltration via deprecated host callback binding in github.com/kubewarden/kubewarden-controller · 11 Mar 2026
  • MediumCVE-2026-29773Kubewarden: Cross-namespace data exfiltration via deprecated host callback binding · 9 Mar 2026
  • LowCVE-2025-24376KubeWarden's AdmissionPolicy and AdmissionPolicyGroup policies can be used to alter PolicyReport resources in github.com/kubewarden/kubewarden-controller · 4 Feb 2025
  • MediumCVE-2025-24376KubeWarden's AdmissionPolicy and AdmissionPolicyGroup policies can be used to alter PolicyReport resources · 30 Jan 2025
github.com/kubewarden/kubewarden-controller security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.