CVE-2026-100705
Description
A flaw was found in Kyverno. Due to missing egress network filtering in its legacy API call handler, an attacker with permission to author policies or submit templated resources can trigger Server-Side Request Forgery (SSRF). This vulnerability allows the attacker to force Kyverno to issue arbitrary network requests to restricted internal endpoints or cloud metadata services, potentially leading to the disclosure of sensitive credentials and confidential internal data.
Statement
IMPORTANT: This vulnerability affects all six recorded Red Hat Konflux components using Kyverno: kyverno-1-15, kyverno-background-1-15, kyverno-cleanup-1-15, kyverno-cli-1-15, kyverno-init-1-15, and kyverno-reports-1-15. Kyverno's legacy apiCall service executor and GlobalContextEntry external-API path do not apply the egress blocklist or validate the configured service URL, allowing an authorized policy author—or, where the URL is templated from an admission resource, a lower-privileged resource submitter—to make Kyverno issue GET or POST requests to arbitrary hosts, including cloud metadata, loopback, and in-cluster services. This can expose cloud credentials and confidential internal data and may permit limited state changes using Kyverno's audience-scoped ServiceAccount token. The CVSS 3.1 score is 7.6 (IMPORTANT), reflecting the high privileges required. Resolution is DELEGATED, and a fix is being pursued.
Mitigation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
