Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-100705— Kyverno before 1.19.1 SSRF via legacy apiCall service executor

Quick assessment

Affected
kyverno kyverno
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

在 Kyverno 1.19.1 版本之前，存在服务器端请求伪造（Server-Side Request Forgery, SSRF）漏洞。 默认出口阻止列表（包括 169.254.169.254、169.254.169.253、metadata.google.internal、127.0.0.0/8 和 ::1/128）以及作用域化令牌（scoped-token）控制机制仅被集成到新的 CEL（通用表达式语言）HTTP GET/POST 库中，而未被应用于传统的 apiCall 服务执行器（位于 pkg/engi

CVSS 7.6 · High EPSS 0.20% · P8
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-100705

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Kyverno before 1.19.1 SSRF via legacy apiCall service executor
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
服务端请求伪造(SSRF)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
kyverno kyverno 0 ~ 1.19.1 -

II. Public POCs for CVE-2026-100705

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-100705

请登录查看更多情报信息。

Other References for CVE-2026-100705 (1)

Other References for CVE-2026-100705 (1)

Same Patch Batch · kyverno · 2026-09-26 · 5 CVEs total

CVE-2026-100706 9.9 CRITICAL kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath
CVE-2026-100704 7.7 HIGH Kyverno before 1.19.1 ImageValidatingPolicy Exception Bypass
CVE-2026-100707 7.7 HIGH Kyverno before 1.19.1 Namespace Isolation Bypass via Percent-Encoded Path
CVE-2026-100703 7.7 HIGH Kyverno before 1.19.1 Cross-Namespace Data Access via globalcontext.Lib

IV. Related Vulnerabilities

Same product: kyverno
Same vendor: kyverno
Same weakness: CWE-918

V. Comments for CVE-2026-100705

No comments yet

Leave a comment