CVE-2025-15613

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-01. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
6.5
EG Score
6.5(high)
EG Risk
60(Attend)
EG Risk 60/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
19%
KEV
Not listed

Published

September 1, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Kyverno before v1.13.4 SSRF via Service Call | Advisories | VulnCheck

https://www.vulncheck.com/advisories/kyverno-before-1.13.4-ssrf-via-service-call
github Patch Available🟡 PoC Available

SSRF via Service Calls · Advisory · kyverno/kyverno · GitHub

https://github.com/kyverno/kyverno/security/advisories/GHSA-459x-q9hg-4gpq

Vendor Advisories for CVE-2025-15613(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/kyverno/kyverno———

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 19× in last 7d / 57× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 20:14 UTCEPSS rescore
  2. 2026-09-20 20:00 UTCGHSA enrichment
  3. 2026-09-19 21:49 UTCEG score recompute
  4. 2026-09-19 21:49 UTCGHSA enrichment
  5. 2026-09-18 23:39 UTCEG score recompute
  6. 2026-09-18 23:39 UTCGHSA enrichment
  7. 2026-09-18 19:27 UTCEPSS rescore
  8. 2026-09-18 01:28 UTCEG score recompute
  9. 2026-09-18 01:28 UTCGHSA enrichment
  10. 2026-09-17 03:17 UTCEG score recompute
  11. 2026-09-17 03:17 UTCGHSA enrichment
  12. 2026-09-16 14:06 UTCEPSS rescore
  13. 2026-09-16 05:13 UTCEPSS rescore
  14. 2026-09-16 05:05 UTCGHSA enrichment
  15. 2026-09-15 06:55 UTCEG score recompute
  16. 2026-09-15 06:55 UTCGHSA enrichment
  17. 2026-09-15 03:08 UTCEPSS rescore
  18. 2026-09-14 08:44 UTCEG score recompute
  19. 2026-09-14 08:44 UTCGHSA enrichment
  20. 2026-09-13 16:45 UTCEPSS rescore
  21. 2026-09-13 10:34 UTCEG score recompute
  22. 2026-09-13 10:34 UTCGHSA enrichment
  23. 2026-09-12 14:59 UTCEPSS rescore
  24. 2026-09-12 12:23 UTCEG score recompute
  25. 2026-09-12 12:23 UTCGHSA enrichment
Show 32 more
  1. 2026-09-11 14:51 UTCEPSS rescore
  2. 2026-09-11 14:12 UTCEG score recompute
  3. 2026-09-11 14:12 UTCGHSA enrichment
  4. 2026-09-11 09:35 UTCEPSS rescore
  5. 2026-09-10 16:02 UTCEG score recompute
  6. 2026-09-10 16:02 UTCGHSA enrichment
  7. 2026-09-10 09:33 UTCEPSS rescore
  8. 2026-09-09 23:39 UTCGHSA enrichment
  9. 2026-09-08 23:27 UTCEG score recompute
  10. 2026-09-08 23:27 UTCGHSA enrichment
  11. 2026-09-08 21:59 UTCEPSS rescore
  12. 2026-09-08 01:06 UTCGHSA enrichment
  13. 2026-09-07 02:56 UTCEG score recompute
  14. 2026-09-07 02:56 UTCGHSA enrichment
  15. 2026-09-06 13:46 UTCEPSS rescore
  16. 2026-09-06 04:43 UTCEG score recompute
  17. 2026-09-06 04:43 UTCGHSA enrichment
  18. 2026-09-05 06:33 UTCEG score recompute
  19. 2026-09-05 06:33 UTCGHSA enrichment
  20. 2026-09-04 13:59 UTCEPSS rescore
  21. 2026-09-04 08:18 UTCEG score recompute
  22. 2026-09-04 08:17 UTCGHSA enrichment
  23. 2026-09-04 05:05 UTCEPSS rescore
  24. 2026-09-03 10:06 UTCEG score recompute
  25. 2026-09-03 10:05 UTCGHSA enrichment
  26. 2026-09-02 14:10 UTCEPSS rescore
  27. 2026-09-02 11:54 UTCGHSA enrichment
  28. 2026-09-01 13:41 UTCEG score recompute
  29. 2026-09-01 13:41 UTCGHSA enrichment
  30. 2026-09-01 12:18 UTCEG score recompute
  31. 2026-09-01 11:43 UTCEG score recompute
  32. 2026-09-01 11:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-15613?
CVE-2025-15613 is a medium vulnerability published on September 1, 2026. 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…
When was CVE-2025-15613 disclosed?
CVE-2025-15613 was first published in the National Vulnerability Database on September 1, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-15613 actively exploited?
CVE-2025-15613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.2% of all scored CVEs.
What is the CVSS score of CVE-2025-15613?
CVE-2025-15613 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-15613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-15613

Explore →

Is Your Infrastructure Affected by CVE-2025-15613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs