OCTOBER 9, 2026
Live Feed
Back to database
Case File

CVE-2026-100705

HIGH · CVSS 7.6 EPSS 0.20% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-09-26 · Last synced 2026-10-09

CyberRota Analysis

AI-Generated

Kyverno versions prior to 1.19.1 are susceptible to server-side request forgery (SSRF), allowing unauthorized users to make arbitrary GET/POST requests to external hosts, including sensitive cloud metadata endpoints and internal services. This vulnerability can lead to exposure of cloud instance credentials and unauthorized access to internal resources, making it critical for organizations using Kyverno to prioritize upgrading to version 1.19.1 or later. Security teams and administrators managing Kubernetes environments should address this issue promptly to mitigate potential data breaches and unauthorized access risks.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

GitHub PoC Links

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-100705
Severity
HIGH
CVSS
7.6
EPSS
0.20%

Original NVD Description

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.