# CVE-2026-4789: CVE-2026-4789

> Attackers can exploit unrestricted CEL HTTP functions in Kyverno to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** BIT-kyverno-2026-4789, ECHO-f9cf-25f6-fcd8, GHSA-rggm-jjmc-3394, GO-2026-5621, MINI-79f7-x45p-7rph, MINI-8gfv-8g4p-9w22, MINI-cj2p-r577-5pj7, MINI-vxv9-m823-v55m

## What is CVE-2026-4789?

CVE-2026-4789 is a critical server-side request forgery vulnerability in Kyverno, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kyverno, versions 1.16.0 and later, are vulnerable to SSRF due to unrestricted CEL HTTP functions.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/kyverno/kyverno` | Go | From 1.16.0 | 1.17.0 |
| `github.com/kyverno/kyverno` | Go | From 1.16.0 | 1.17.0 |
| `github.com/kyverno/kyverno` | Go | From 1.16.0 | 1.17.0 |
| `kyverno` | Bitnami | From 1.16.0 | 1.17.2 |

Products: Kyverno Kyverno.

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

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

## Is CVE-2026-4789 being exploited?

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

## Other vulnerabilities in Kyverno

- [CVE-2026-22039](https://insights.sbomify.com/CVE-2026-22039/): Kyverno Cross-Namespace Privilege Escalation via Policy apiCall (critical 10.0)
- [CVE-2025-46342](https://insights.sbomify.com/CVE-2025-46342/): Kyverno vulnerable to bypass of policy rules that use namespace selectors in match statements (high 8.6)
- [CVE-2026-41323](https://insights.sbomify.com/CVE-2026-41323/): Kyverno: ServiceAccount token leaked to external servers via apiCall service URL (high 8.1)
- [CVE-2026-40868](https://insights.sbomify.com/CVE-2026-40868/): kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token (high 8.1)
- [CVE-2022-47633](https://insights.sbomify.com/CVE-2022-47633/): kyverno verifyImages rule bypass possible with malicious proxy/registry (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4789 is a critical server-side request forgery vulnerability in Kyverno, published on 30 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4789 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/kyverno/kyverno (Go): affected from 1.16.0; fixed in 1.17.0
- github.com/kyverno/kyverno (Go): affected from 1.16.0; fixed in 1.17.0
- github.com/kyverno/kyverno (Go): affected from 1.16.0; fixed in 1.17.0
- kyverno (Bitnami): affected from 1.16.0; fixed in 1.17.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-4789/ (Markdown: https://insights.sbomify.com/CVE-2026-4789/index.md)
```

## Sources

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

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