Server-Side Request Forgery (SSRF) Affecting kyverno-cleanup-controller-compat-1.13 package, versions *


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.2% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-KYVERNOCLEANUPCONTROLLERCOMPAT113-20375586
  • published2 Oct 2026
  • disclosed26 Sept 2026

Introduced: 26 Sep 2026

NewCVE-2026-100705  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest kyverno-cleanup-controller-compat-1.13.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kyverno-cleanup-controller-compat-1.13 package and not the kyverno-cleanup-controller-compat-1.13 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

Kyverno before 1.19.1 is vulnerable to server-side request forgery. The default egress blocklist (169.254.169.254, 169.254.169.253, metadata.google.internal, 127.0.0.0/8, ::1/128) and the scoped-token control were wired only into the new CEL http.Get/Post library and were never applied to the legacy apiCall service executor (pkg/engine/apicall/executor.go) or to the GlobalContextEntry external-API path, which handle every non-CEL context[].apiCall.service call. Because these paths use a plain net/http client with no egress filtering and no validation of the configured service URL, a ClusterPolicy or GlobalContextEntry author — or, where a deployed policy templates the service URL from the admission resource, a lower-privileged resource submitter — can cause Kyverno to issue GET/POST requests to an arbitrary host, including the cloud metadata endpoint, loopback, and any in-cluster service, reading cloud instance credentials and reaching internal endpoints with Kyverno's network position. The executor also unconditionally attaches Kyverno's projected ServiceAccount token to the attacker-chosen destination; the token is audience-scoped, limiting its replay value. Fixed in 1.19.1.

CVSS Base Scores

version 3.1