cve.bz

CVE-2025-15613 kyverno kyverno: SSRF

6.9 mediumEPSS 0.4%

Medium (6.9) in kyverno kyverno. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 30th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-09-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-15613 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-15613?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-15613?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-15613 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
kyvernobefore 1.13.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-459x-q9hg-4gpqGogithub.com/kyverno/kyverno<=1.13.4no fix published
GO-2025-3615Gogithub.com/kyverno/kyvernoall versionsno fix published

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A server-side request forgery (SSRF) vulnerability was found in Kyverno, a policy engine for Kubernetes. In versions prior to 1.13.4, an attacker with permission to create or modify Kyverno ClusterPolicies or Policies can specify an external URL in a policy's apiCall/service configuration. Although the Service Call feature is documented for in-cluster services only, it also resolves external addresses, allowing HTTP requests to an attacker-controlled server. Because policy context data, including the contents of Kubernetes resources such as secrets and configuration maps, is sent in these requests, an attacker can exfiltrate sensitive cluster data. This SSRF vulnerability can also be exploited to access cloud provider metadata APIs (such as AWS, GCP, or Azure instance metadata endpoints) or to enumerate internal cluster services. This issue affects Red Hat Konflux Pipeline, which uses Kyverno for policy enforcement.

Red Hat's mitigation

This issue is fixed in Kyverno version 1.13.4. Red Hat will provide updated versions of Konflux Pipeline that include the fixed Kyverno version.

Until updates are available, administrators can reduce the risk of SSRF attacks by implementing the following mitigations:

1. Restrict the set of users who can create or modify Kyverno ClusterPolicies and Policies. Use Kubernetes RBAC to limit policy creation permissions to trusted cluster administrators only.

2. Implement network policies to restrict egress traffic from the Kyverno namespace. Block outbound connections to external networks and cloud metadata endpoints (such as 169.254.169.254) to prevent SSRF-based data exfiltration.

3. Review existing Kyverno policies for suspicious apiCall/service configurations that reference external URLs or cloud metadata endpoints. Remove or modify any policies that contain unexpected external service calls.

4. Enable audit logging for Kyverno policy creation and modification events to detect unauthorized policy changes.

5. Monitor network traffic from Kyverno pods for unexpected outbound connections, particularly to external IP addresses or cloud metadata endpoints.

6. Consider temporarily disabling the Service Call feature in Kyverno if it is not required for policy enforcement in your environment.

7. Upgrade to Kyverno 1.13.4 or later as soon as updated Konflux Pipeline packages are available from Red Hat.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-15613.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON