Is CVE-2026-84196 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-84196 being exploited in the wild.

How severe is CVE-2026-84196?

High severity, with a CVSS score of 7.7, published 1 September 2026.

Which products and versions are affected?

github.com/kyverno/kyverno (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.17.1; Kyverno before 1.18.0.

Is there a fix for CVE-2026-84196?

A patch was published on 2026-04-13: Patch available in version 1.18.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-84196 attacked?

It is attacked over the network.

Am I affected by CVE-2026-84196?

Check whether you run github.com/kyverno/kyverno (Go) or Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-84196: Kyverno server-side request forgery in apiCall

CVE-2026-84196 · Severity: high · CVSS 7.7 · Published 2026-09-01

Kyverno is a policy engine for Kubernetes that validates and controls container deployments. A vulnerability in its apiCall feature allows authenticated users to send arbitrary HTTP requests to internal services and cloud metadata endpoints, potentially exposing sensitive credentials and configuration data. Response data is reflected back in error messages, making data theft straightforward for attackers with cluster access.

Technologies: github.com/kyverno/kyverno (Go), Kyverno. Vendors: Go, Kyverno.

Quick answers

Is CVE-2026-84196 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-84196 being exploited in the wild.
How severe is CVE-2026-84196?: High severity, with a CVSS score of 7.7, published 1 September 2026.
Which products and versions are affected?: github.com/kyverno/kyverno (Go) SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.17.1; Kyverno before 1.18.0.
Is there a fix for CVE-2026-84196?: A patch was published on 2026-04-13: Patch available in version 1.18.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-84196 attacked?: It is attacked over the network.
Am I affected by CVE-2026-84196?: Check whether you run github.com/kyverno/kyverno (Go) or Kyverno at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A server-side request forgery (SSRF) vulnerability exists in Kyverno's apiCall.service.url when used with variable substitution. The vulnerability stems from lack of URL validation and IP filtering in the HTTP client, allowing authenticated users to inject attacker-controlled input via resource annotations or other metadata fields. Requests can target loopback addresses (127.0.0.1), link-local addresses (169.254.0.0/16), AWS IMDS, and internal ClusterIP services. The HTTP client follows up to 10 redirects without re-validation, and response data from non-2xx responses or JSON parsing failures is reflected in admission error messages, enabling non-blind data exfiltration. Authentication is required (cluster user), but attack complexity is low. Patch is available in version 1.18.0.

Affected products

Kyverno Kyverno before 1.18.0

Identifiers

CVE-2026-84196
GHSA-qr4g-8hrp-c4rw
GO-2026-5594

Timeline

2026-04-13: advisory: GitHub security advisory published
2026-09-01: disclosed: CVE-2026-84196 published on NVD
2026-04-13: patched: Patch available in version 1.18.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.