CVE-2026-84199
Received Received - Intake

Kyverno SSRF Vulnerability in APICall Feature

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: VulnCheck

Description
Kyverno before 1.16.2 contains a server-side request forgery (SSRF) vulnerability in the APICall feature. The URL field in a Policy's ServiceCall configuration is not validated, so a user with namespace-level Policy creation permissions can direct Kyverno to make HTTP requests to arbitrary internal resources (e.g., cloud metadata endpoints such as 169.254.169.254 or other tenants' resources). Because Kyverno executes these requests using its cluster-wide high-privilege ServiceAccount (a Confused Deputy problem), the responses—potentially including other tenants' secrets and cloud IAM credentials—are returned in the PolicyReport and can be read by the attacker, breaking multi-tenant isolation.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-01
Last Modified
2026-09-01
Generated
2026-09-01
AI Q&A
2026-09-01
EPSS Evaluated
N/A
NVD
CVE-2026-84199
EUVD
EUVD-2026-69034

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
kyverno kyverno to 1.16.2 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Server-Side Request Forgery (SSRF) vulnerability in Kyverno versions before 1.16.2. It allows users with namespace-level Policy creation permissions to direct Kyverno to make HTTP requests to arbitrary internal resources using its high-privilege ServiceAccount. The URL field in Policy configuration is not validated, enabling access to sensitive data like other tenants' secrets or cloud IAM credentials, which are then included in PolicyReports accessible to the attacker.

Detection Guidance

To detect this vulnerability, check Kyverno versions before 1.16.2 using commands like 'kyverno version' or inspect Pod logs for APICall feature usage. Monitor PolicyReports for unexpected external or internal HTTP requests in Kyverno logs.

Impact Analysis

An attacker with namespace-level permissions can exploit this to steal sensitive data from other tenants or cloud metadata services. This includes secrets, API keys, database passwords, and cloud IAM credentials. The attacker can access this data through PolicyReports without needing cluster-admin privileges, breaking multi-tenant isolation and potentially enabling lateral movement to cloud environments.

Compliance Impact

This vulnerability can lead to severe compliance violations. It breaks multi-tenant isolation, potentially exposing personal data (GDPR) or protected health information (HIPAA). Unauthorized access to credentials or secrets may also violate data protection requirements for confidentiality and integrity, leading to regulatory fines and legal consequences.

Mitigation Strategies

Immediately disable the APICall feature in Kyverno configurations. Restrict Policy creation permissions to cluster-admin only. Apply NetworkPolicy to limit Kyverno Pod egress traffic to trusted endpoints.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-84199. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart