CVE-2026-100705
Last modified
CVE-2026-100705 is a high-severity vulnerability rated 7.6/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| kyverno | kyverno | < 1.19.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-100705?
How severe is CVE-2026-100705?
How do I fix CVE-2026-100705?
How Strix Helps
- One Click Account Takeover in GranolaHow a notification link broke out of Electron and led to a one-click account takeover.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-10070A vulnerability was found in macrozheng mall up to 1.0.3. Th…5.1
- CVE-2026-100700nodemailer before 10.0.6 contains a denial of service vulner…7.5
- CVE-2026-100701Nodemailer versions 5.0.0 through 10.0.1 use a process-globa…5.9
- CVE-2026-100702Nodemailer before 10.0.2 fails to properly flatten deeply ne…5.9
- CVE-2026-100703Kyverno 1.16.0 through 1.19.0 registers the globalcontext.Li…7.7
- CVE-2026-100704Kyverno is a policy engine for Kubernetes. In versions 1.14.…7.7
- CVE-2026-100706kyverno before 1.19.1 fails to properly validate URL-encoded…9.9
- CVE-2026-100707Kyverno before 1.19.1 contains a namespace isolation bypass …7.7
- CVE-2026-100708Froxlor before 2.3.13 returns the ssl_key_file column — whic…7.1
- CVE-2026-100709Froxlor through 2.3.10 stores only a numeric user ID in reme…7.5
- CVE-2026-10071DreamMaker developed by Interinfo has an Arbitrary File Uplo…9.8
- CVE-2026-100710Froxlor through 2.3.10 does not filter sensitive columns fro…4.9
Are you affected by CVE-2026-100705?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
