Is CVE-2026-41323 exploited in the wild?

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

How severe is CVE-2026-41323?

High severity, with a CVSS score of 8.1, published 24 April 2026.

Which products and versions are affected?

github.com/kyverno/kyverno (Go) < 1.17.0, SEMVER:introduced=0,fixed=1.17.0.

Is there a fix for CVE-2026-41323?

Yes. github.com/kyverno/kyverno (Go): upgrade to 1.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-41323?

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-41323: Kyverno: ServiceAccount token leaked to external servers via apiCall service URL

Q: Is there a fix for CVE-2026-41323?

Yes. github.com/kyverno/kyverno (Go): upgrade to 1.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: Am I affected by CVE-2026-41323?

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-41323 · Severity: high · CVSS 8.1 · Published 2026-04-24

Kyverno is a policy engine designed for cloud native platform engineering teams. Prior to versions 1.18.0-rc1, 1.17.2-rc1, and 1.16.4, Kyverno's apiCall feature in ClusterPolicy automatically attaches the admission controller's ServiceAccount token to outgoing HTTP requests. The service URL has no validation — it can point anywhere, including attacker-controlled servers. Since the admission controller SA has permissions to patch webhook configurations, a stolen token leads to full cluster compromise. Versions 1.18.0-rc1, 1.17.2-rc1, and 1.16.4 patch the issue.

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

Quick answers

Is CVE-2026-41323 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41323 being exploited in the wild.
How severe is CVE-2026-41323?: High severity, with a CVSS score of 8.1, published 24 April 2026.
Which products and versions are affected?: github.com/kyverno/kyverno (Go) < 1.17.0, SEMVER:introduced=0,fixed=1.17.0.
Is there a fix for CVE-2026-41323?: Yes. github.com/kyverno/kyverno (Go): upgrade to 1.17.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-41323?: 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.

How to fix

github.com/kyverno/kyverno (Go): upgrade to 1.17.0 or later
```
go get github.com/kyverno/kyverno@v1.17.0
```

Affected products

github.com/kyverno/kyverno (Go) < 1.17.0, SEMVER:introduced=0,fixed=1.17.0
Kyverno

Identifiers

CVE-2026-41323
GHSA-f9g8-6ppc-pqq4
GO-2026-5351

References

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