Is CVE-2026-100705 exploited in the wild?

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

How severe is CVE-2026-100705?

High severity, with a CVSS score of 7.6, published 26 September 2026.

Is there a fix for CVE-2026-100705?

A patch was published on 2026-09-26: Version 1.19.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-100705 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-100705?

Check whether you run 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-100705: Kyverno server-side request forgery in apiCall executor

CVE-2026-100705 · Severity: high · CVSS 7.6 · Published 2026-09-26

Kyverno is a policy engine that enforces security rules in Kubernetes clusters. A flaw in how it handles policy configuration allows attackers with policy authoring rights to force Kyverno to make arbitrary outbound network requests to internal systems and cloud metadata services, potentially exposing cloud credentials and allowing access to internal infrastructure that should be protected.

Technologies: Kyverno. Vendors: Kyverno.

Quick answers

Is CVE-2026-100705 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-100705 being exploited in the wild.
How severe is CVE-2026-100705?: High severity, with a CVSS score of 7.6, published 26 September 2026.
Which products and versions are affected?: Kyverno before 1.19.1.
Is there a fix for CVE-2026-100705?: A patch was published on 2026-09-26: Version 1.19.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-100705 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-100705?: Check whether you run 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

The legacy apiCall service executor and GlobalContextEntry external-API path bypass SSRF protections (egress blocklist for 169.254.169.254, metadata services, and loopback) that were only applied to the newer CEL http library. An attacker who can author a ClusterPolicy or GlobalContextEntry—or submit resources templated with a service URL—can cause Kyverno's net/http client to reach arbitrary hosts and leak Kyverno's projected ServiceAccount token to attacker-controlled destinations, with no egress filtering or URL validation in place.

Affected products

Kyverno Kyverno before 1.19.1

Timeline

2026-09-26: disclosed
2026-09-26: patched: Version 1.19.1

References

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