80 matches found
BIT-KYVERNO-2026-100707 Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded Path
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path interpretation between validation and execution. A low-privilege tenant can use percent-encoded dot-segments in urlPath to bypass namespace checks and...
BIT-KYVERNO-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath
kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing namespace tenants to bypass the per-namespace clamp and create objects in other namespaces as the admission-controller ServiceAccount. Attackers can exploit this by using percent-encoded...
BIT-KYVERNO-2026-100705 Kyverno before 1.19.1 SSRF via legacy apiCall service executor
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 legac...
CVE-2026-100705
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 legac...
EUVD-2026-87680
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path interpretation between validation and execution. A low-privilege tenant can use percent-encoded dot-segments in urlPath to bypass namespace checks and...
CVE-2026-100707
Versions of Kyverno prior to 1.19.1 are vulnerable to a namespace isolation bypass within the apiCall context entry of namespaced Policy resources. The root cause is an inconsistent path interpretation between the validation and execution phases. A low-privilege tenant can exploit this by using p...
CVE-2026-100707 Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded Path
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path interpretation between validation and execution. A low-privilege tenant can use percent-encoded dot-segments in urlPath to bypass namespace checks and...
CVE-2026-100707 Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded Path
Kyverno before 1.19.1 contains a namespace isolation bypass in the apiCall context entry of namespaced Policy resources due to inconsistent path interpretation between validation and execution. A low-privilege tenant can use percent-encoded dot-segments in urlPath to bypass namespace checks and...
EUVD-2026-87679
kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing namespace tenants to bypass the per-namespace clamp and create objects in other namespaces as the admission-controller ServiceAccount. Attackers can exploit this by using percent-encoded...
CVE-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath
kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing namespace tenants to bypass the per-namespace clamp and create objects in other namespaces as the admission-controller ServiceAccount. Attackers can exploit this by using percent-encoded...
CVE-2026-100706
Kyverno versions before 1.19.1 are vulnerable to privilege escalation due to improper validation of URL-encoded path segments in the Policy apiCall urlPath. This flaw allows namespace tenants to bypass per-namespace clamps and perform actions as the admission-controller ServiceAccount . By using ...
CVE-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath
kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing namespace tenants to bypass the per-namespace clamp and create objects in other namespaces as the admission-controller ServiceAccount. Attackers can exploit this by using percent-encoded...
CVE-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath
kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing namespace tenants to bypass the per-namespace clamp and create objects in other namespaces as the admission-controller ServiceAccount. Attackers can exploit this by using percent-encoded...
CVE-2026-100705
Kyverno versions before 1.19.1 are vulnerable to server-side request forgery (SSRF) due to a lack of egress filtering and URL validation in the legacy apiCall service executor (pkg/engine/apicall/executor.go) and the GlobalContextEntry external-API path. While new CEL libraries include a default ...
CVE-2026-100705 Kyverno before 1.19.1 SSRF via legacy apiCall service executor
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 legac...
CVE-2026-100705 Kyverno before 1.19.1 SSRF via legacy apiCall service executor
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 legac...
EUVD-2026-87678
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 legac...
CVE-2026-100705 Kyverno before 1.19.1 SSRF via legacy apiCall service executor
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 legac...
PT-2026-99378
Name of the Vulnerable Software and Affected Versions Kyverno versions prior to 1.19.1 Description An issue exists in the apiCall context entry of namespaced Policy resources caused by inconsistent path interpretation between validation and execution. A low-privilege tenant can utilize...
BIT-KYVERNO-2026-84195 Kyverno before 1.16.4 Credential Leak via apiCall
Kyverno before 1.16.4 automatically attaches the admission controller's ServiceAccount token to outbound HTTP requests in apiCall service mode without explicit authorization headers. Attackers can exfiltrate the token by directing apiCall requests to external or attacker-controlled endpoints,...