# CVE-2026-84199: Kyverno before 1.16.2 SSRF via APICall Feature

> Attackers with policy creation rights can exploit SSRF in Kyverno to access internal resources and steal cloud credentials via high-privilege service accounts.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** BIT-kyverno-2026-84199, ECHO-3fbf-c265-77f3, GHSA-fmqp-4wfc-w3v7, GHSA-q5v3-pp68-6crj, GO-2026-5371, MINI-23xr-wxc2-3wj8, MINI-3jpr-9p87-j6xc, MINI-4c7r-f5cw-q8vr, MINI-4xj9-3w3c-32w2, MINI-54j2-chvw-v5q8, MINI-5j55-3xvh-pjxq, MINI-5xq5-3cr9-cq63, MINI-6mqw-vrm6-v649, MINI-8462-64h2-r3hr, MINI-935r-g6h5-hxcw, MINI-99jh-3p68-gvw6, MINI-9fwq-wvww-332x, MINI-9grv-7c9r-37w3, MINI-9gxq-pq5v-mw3r, MINI-fxhw-c497-397q, MINI-m6v2-v4mw-r64c, MINI-p3j5-4rx7-qv8g, MINI-pmq7-8f38-3rw3, MINI-qcx2-g74x-9p79, MINI-wq4v-qq9v-5xxw, MINI-wqf5-gwx8-6jmj, MINI-x6vw-c9jg-q779

## What is CVE-2026-84199?

CVE-2026-84199 is a medium-severity server-side request forgery vulnerability in kyverno, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kyverno before 1.16.2 contains a server-side request forgery (SSRF) vulnerability in the APICall feature. The URL field in a Policy's ServiceCall configuration is not validated, so a user with namespace-level Policy creation permissions can direct Kyverno to make HTTP requests to arbitrary internal resources (e.g., cloud metadata endpoints such as 169.254.169.254 or other tenants' resources). Because Kyverno executes these requests using its cluster-wide high-privilege ServiceAccount (a Confused Deputy problem), the responses—potentially including other tenants' secrets and cloud IAM credentials—are returned in the PolicyReport and can be read by the attacker, breaking multi-tenant isolation.

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

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

4 open source packages ship an affected version, including github.com/kyverno/kyverno and kyverno.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kyverno/kyverno` | Go | All versions | 1.16.2 |
| `github.com/kyverno/kyverno` | Go | All versions | 1.16.2 |
| `github.com/kyverno/kyverno` | Go | All versions | 1.16.2 |
| `kyverno` | Bitnami | All versions | 1.16.2 |

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

Upgrade github.com/kyverno/kyverno to 1.16.2 or later.

## Is CVE-2026-84199 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84199 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84199 is a medium-severity server-side request forgery vulnerability in kyverno, published on 1 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-84199 exists.

Affected packages and fixed versions:
- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.16.2
- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.16.2
- github.com/kyverno/kyverno (Go): affected all versions; fixed in 1.16.2
- kyverno (Bitnami): affected all versions; fixed in 1.16.2

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-84199/ (Markdown: https://insights.sbomify.com/CVE-2026-84199/index.md)
```

## Sources

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

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