CVE-2026-100705
published 2026-09-26CVE-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…
PriorityP347high7.6CVSS 3.1
AVNACLPRHUINSCCHILAN
EPSS
0.20%
9.3th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| kyverno | kyverno | < 1.19.1 | 1.19.1 |
CVSS provenance
nvdv3.17.6HIGHCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
nvdv4.08.3HIGHCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
vendor_redhat7.6HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
Kyverno before 1.19.1 is vulnerable to server-side request forgery.
ghsa_unreviewed·2026-09-26
CVE-2026-100705 [HIGH] CWE-918 Kyverno before 1.19.1 is vulnerable to server-side request forgery.
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 reques
VulDB
Kyverno up to 1.19.0 Legacy ApiCall Service Executor executor.go server-side request forgery
vuldb·2026-09-26·CVSS 7.6
CVE-2026-100705 [HIGH] Kyverno up to 1.19.0 Legacy ApiCall Service Executor executor.go server-side request forgery
A vulnerability was found in Kyverno up to 1.19.0 and classified as critical. This impacts an unknown function of the file pkg/engine/apicall/executor.go of the component Legacy ApiCall Service Executor. The manipulation results in server-side request forgery.
This vulnerability is cataloged as CVE-2026-100705. The attack may be launched remotely. There is no exploit available.
It is suggested to upgrade the affected component.
Red Hat
github.com/kyverno/kyverno: Kyverno: Server-Side Request Forgery via legacy API call executor
vendor_redhat·2026-09-26·CVSS 7.6
CVE-2026-100705 [HIGH] CWE-918 github.com/kyverno/kyverno: Kyverno: Server-Side Request Forgery via legacy API call executor
github.com/kyverno/kyverno: Kyverno: Server-Side Request Forgery via legacy API call 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 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 admissi
No detection rules found.
No public exploits indexed.
2026-09-26
Published