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

> Attackers can exploit SSRF in Kyverno's legacy API executor to access cloud metadata and internal services, bypassing egress controls.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** BIT-kyverno-2026-100705, GHSA-8x9j-8h3w-5cxq, GHSA-q825-p383-r9v5, MINI-3r9p-75wf-5qrw, MINI-4ppp-fc7f-x4vc, MINI-83rm-v4hm-m3rw, MINI-87j7-whfg-q863, MINI-9h3w-v9p6-mcp4, MINI-f892-vqxc-f2jm, MINI-g7w6-4rg7-x5f8, MINI-h6cp-735j-7x2x, MINI-hqvr-6g6v-9546, MINI-ppv5-8h9v-64q8, MINI-r5qx-2pfh-xq93, MINI-vj9c-9454-hrq6, MINI-x9w5-wmr8-f59v

## What is CVE-2026-100705?

CVE-2026-100705 is a high-severity server-side request forgery vulnerability in kyverno, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-100705?

1 open source package ship an affected version, including kyverno.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kyverno` | Bitnami | All versions | 1.19.1 |

## How do I fix CVE-2026-100705?

Upgrade kyverno to 1.19.1 or later.

## Is CVE-2026-100705 being exploited?

There is no known exploitation of CVE-2026-100705 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100705 and fix it if it is affected.

What it is: CVE-2026-100705 is a high-severity server-side request forgery vulnerability in kyverno, published on 26 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100705 in the wild and no public exploit code.

Affected packages and fixed versions:
- kyverno (Bitnami): affected all versions; fixed in 1.19.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100705/ (Markdown: https://insights.sbomify.com/CVE-2026-100705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100705
- OSV: https://osv.dev/vulnerability/CVE-2026-100705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100705/
Summaries are generated and may contain mistakes; the official description above is the record.