Kyverno Policy SSRF Enables Unauthorized Internal Resource Access

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 331matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Kyverno before version 1.16.2 contains a server-side request forgery (SSRF) vulnerability in its APICall feature that allows attackers to exploit insufficient URL validation in Policy ServiceCall configurations. Users with namespace-level Policy creation permissions can craft malicious policies that direct Kyverno to make HTTP requests to arbitrary internal resources, including cloud metadata endpoints (169.254.169.254) and other sensitive infrastructure. This is particularly dangerous because Kyverno executes these requests using its cluster-wide, high-privilege ServiceAccount, effectively giving attackers the ability to steal cloud credentials, access secrets, pivot to other tenants' resources, and gather sensitive infrastructure information. Any organization running vulnerable versions of Kyverno with multi-tenant environments or cloud-integrated deployments faces significant risk of credential compromise and lateral movement.

Casky's 331 matched security skills leverage Claude's extended reasoning to detect the reconnaissance and exploitation patterns underlying this vulnerability across MITRE ATT&CK techniques TA0001 (Reconnaissance) and TA0006 (Credential Access). Practitioners using Casky would identify suspicious policy creation activities, unusual outbound HTTP requests from Kyverno's ServiceAccount to metadata endpoints or internal IPs, and unexpected credential exfiltration patterns. The platform's skills would flag policy definitions containing unvalidated URL fields, detect anomalous network traffic to 169.254.169.254 or internal CIDR ranges, and surface indicators of cloud credential theft. By correlating policy creation events with subsequent high-privilege API calls or external network communications, Casky enables security teams to catch SSRF exploitation attempts before attackers leverage stolen credentials for deeper cluster compromise and multi-tenant resource access.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

331 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-84199.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0006

Investigate the attack patterns behind CVE-2026-84199

Casky has 331 skills that investigate the attack patterns behind CVE-2026-84199. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn