Is CVE-2025-15613 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-15613 being exploited in the wild.

How severe is CVE-2025-15613?

Medium severity, with a CVSS score of 6.5, published 1 September 2026.

Which products and versions are affected?

github.com/kyverno/kyverno (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.13.4; Kyverno before v1.13.4.

Is there a fix for CVE-2025-15613?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2025-15613 attacked?

It is attacked over the network.

Am I affected by CVE-2025-15613?

Check whether you run github.com/kyverno/kyverno (Go) or Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-15613: Kyverno server-side request forgery via Service Calls

CVE-2025-15613 · Severity: medium · CVSS 6.5 · Published 2026-09-01

Kyverno is a policy engine for Kubernetes that allows administrators to enforce security and compliance rules on container deployments. A flaw in its Service Call functionality allows an attacker with permission to create cluster policies to send requests to external servers controlled by the attacker, exfiltrating sensitive cluster data including Kubernetes secrets. This affects organizations using Kyverno for policy enforcement across their Kubernetes infrastructure.

Technologies: github.com/kyverno/kyverno (Go), Kyverno. Vendors: Go, Kyverno.

Quick answers

Is CVE-2025-15613 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-15613 being exploited in the wild.
How severe is CVE-2025-15613?: Medium severity, with a CVSS score of 6.5, published 1 September 2026.
Which products and versions are affected?: github.com/kyverno/kyverno (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.13.4; Kyverno before v1.13.4.
Is there a fix for CVE-2025-15613?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-15613 attacked?: It is attacked over the network.
Am I affected by CVE-2025-15613?: Check whether you run github.com/kyverno/kyverno (Go) or Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

Kyverno's Service Call functionality is intended to reach internal Kubernetes services but fails to restrict requests to in-cluster addresses, allowing resolution of external URLs. The vulnerability is a server-side request forgery (CWE-918) in the apiCall/service configuration of ClusterPolicy and Policy resources. An attacker with policy creation permissions (typically cluster administrators but potentially lower-privileged users in multi-tenant environments) can craft a policy that sends HTTP POST requests containing policy context data—including Kubernetes resource contents and secrets—to an attacker-controlled external server. No special network configuration is required; the attack requires only the ability to create or modify cluster policies. Patches are available in version 1.13.4 and later.

Affected products

Kyverno Kyverno before v1.13.4

Identifiers

CVE-2025-15613
GHSA-459x-q9hg-4gpq
GO-2025-3615

Timeline

2025-04-15: disclosed: GitHub Security Advisory GHSA-459x-q9hg-4gpq published
2026-09-01: advisory: CVE-2025-15613 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.