ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-84199

Kyverno APICall SSRF Vulnerability Leading to Multi-Tenant Isolation Breach in github.com/kyverno/kyverno

Published Apr 14, 2026 · catalog updated Oct 14, 2026 · Kyverno APICall SSRF Vulnerability

Check if you run it

No confirmed exploitation is on record for CVE-2026-84199. EPSS is 0.36%. Act only if a listed version of Kyverno APICall SSRF Vulnerability is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Kyverno APICall SSRF Vulnerability).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.36%
Remediation
Advisory link
Affected products
Go github.com/kyverno/kyverno

### Summary Kyverno's APICall feature contains a Server-Side Request Forgery (SSRF) vulnerability that allows users with Policy creation permissions to access arbitrary internal resources through Kyverno's high-privilege ServiceAccount. In multi-tenant Kubernetes environments, this constitutes a classic Confused Deputy problem: low-privilege tenants can steal sensitive data from other tenants (such as database passwords and API keys) and cloud platform IAM credentials, completely breaking tenant isolation. This vulnerability does not require cluster-admin privileges and can be exploited with only namespace-level Policy creation permissions. ### Details #### Vulnerability Mechanism Kyverno's APICall feature allows Policies to fetch external data via HTTP requests. This feature does not validate target URLs when executing HTTP requests, leading to an SSRF vulnerability. **Source Point - User-Controlled URL** File: , lines 247-250 The URL field is completely controlled by users through Policy configuration, with no validation mechanism to restrict target addresses. **Sink Point - HTTP Request Execution** File: , lines 65-110 Line 80's directly executes the HTTP request without checking if the target URL is an internal IP address (like 169.254.169.254) or resources belonging to other tenants. **Confused Deputy Problem** In multi-tenant environments, Kyverno uses a cluster-wide high-privilege ServiceAccount to execute all APICall requests. When a low-privilege tenant creates a Policy containing malicious APICall directives, Kyverno executes these requests with its own high privileges, leading to privilege escalation. Attack path: ### PoC #### Environment Setup **Prerequisites** - Kubernetes cluster - Kyverno v1.16.0 installed - Mock cloud metadata service (optional, for testing cloud credential theft) **Step 1: Install Kyverno** Verify installation: **Step 2: Deploy Mock Metadata Service** Create file : Deploy: **Step 3: Create Multi-Tenant Environment** Create two tenan

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Go github.com/kyverno/kyverno0 → 1.16.2

How to fix CVE-2026-84199

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-84199. EPSS is 0.36%. Act only if a listed version of Kyverno APICall SSRF Vulnerability is installed.

Which versions are affected?

Compare what you have installed with 0 → 1.16.2. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.36%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 25, 2026 · GitHub Advisory Database

    Detected

    Kyverno APICall SSRF Vulnerability Leading to Multi-Tenant Isolation Breach in github.com/kyverno/kyverno

  2. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    github.com/kyverno/kyverno fixed in 1.16.2

  3. Oct 14, 2026 · GitHub Advisory Database

    Fix available

    github.com/kyverno/kyverno fixed in 1.16.2

  4. Oct 14, 2026 · GitHub Advisory Database

    Updated

    Kyverno APICall SSRF Vulnerability Leading to Multi-Tenant Isolation Breach in github.com/kyverno/kyverno

Sources

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.