CVE-2025-15613
Received Received - Intake

Kyverno SSRF Vulnerability Exposes Cluster Data

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: VulnCheck

Description
Kyverno before v1.13.4 is vulnerable to server-side request forgery (SSRF) via its Service Call functionality. An attacker with permission to create Kyverno (Cluster)Policies can specify an external URL in a policy's apiCall/service configuration; although Service Call is documented for in-cluster services, it also resolves external addresses, allowing requests to an attacker-controlled server. Because policy context data (including contents of Kubernetes resources such as secrets) is sent in these requests, an attacker can exfiltrate sensitive cluster data.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-01
Last Modified
2026-09-01
Generated
2026-09-01
AI Q&A
2026-09-01
EPSS Evaluated
N/A
NVD
CVE-2025-15613
EUVD
EUVD-2025-210816

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
kyverno kyverno to 1.13.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2025-15613 is a Server-Side Request Forgery (SSRF) vulnerability in Kyverno, a Kubernetes policy engine. It allows attackers with permission to create Kyverno policies to exploit the Service Call functionality to make requests to external servers under their control. This can lead to data exfiltration, including sensitive information like Kubernetes secrets.

Detection Guidance

To detect this vulnerability, check Kyverno versions prior to v1.13.4 by running: kubectl get deployment -n kyverno kyverno -o jsonpath='{.spec.template.spec.containers[0].image}'. If the version is less than 1.13.4, the system is vulnerable. Inspect Kyverno policies for external URLs in apiCall/service configurations using: kubectl get clusterpolicy -o yaml | grep -A 5 "apiCall:" or kubectl get clusterpolicy -o yaml | grep -A 5 "service:"

Monitor network traffic from Kyverno pods for unexpected outbound connections to external IPs using: kubectl logs -n kyverno <kyverno-pod-name> --tail=100 | grep -i "http" or tcpdump -i any -n port 80 or 443 and host not <cluster-ip-range>

Impact Analysis

An attacker could exfiltrate sensitive cluster data, including Kubernetes secrets, by crafting a malicious policy that sends requests to an attacker-controlled server. This could lead to unauthorized access to confidential information or further compromise of the Kubernetes environment.

Compliance Impact

This vulnerability could lead to unauthorized exposure of sensitive data, such as personally identifiable information (PII) or protected health information (PHI), violating compliance requirements like GDPR or HIPAA. Organizations using affected Kyverno versions may face regulatory penalties or reputational damage.

Mitigation Strategies

Upgrade Kyverno to v1.13.4 or later immediately using: helm upgrade kyverno kyverno/kyverno --namespace kyverno --version 1.13.4 or kubectl apply -f https://github.com/kyverno/kyverno/releases/download/v1.13.4/install.yaml

Restrict permissions for creating Kyverno policies to trusted users only. Audit existing policies for unauthorized external URLs in apiCall/service configurations and remove any suspicious entries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-15613. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart