# CVE-2026-41323: Kyverno: ServiceAccount token leaked to external servers via apiCall service URL

Source: https://junglewise.ai/threats/cve-2026-41323-kyverno-serviceaccount-token-leaked-to-external-servers-via  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-24. Updated: 2026-05-11  
License: CC BY 4.0 with a link back

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)](https://junglewise.ai/threats/technologies/github-com-kyverno-kyverno), [Kyverno](https://junglewise.ai/threats/technologies/kyverno). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Kyverno](https://junglewise.ai/threats/vendors/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

  ```sh
  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

- [https://api.github.com/users/KoreaSecurity](https://api.github.com/users/KoreaSecurity)
- [https://github.com/KoreaSecurity](https://github.com/KoreaSecurity)
- [https://api.github.com/users/KoreaSecurity/gists%7B/gist_id%7D](https://api.github.com/users/KoreaSecurity/gists%7B/gist_id%7D)
- [https://api.github.com/users/KoreaSecurity/repos](https://api.github.com/users/KoreaSecurity/repos)
- [https://avatars.githubusercontent.com/u/8425791?v=4](https://avatars.githubusercontent.com/u/8425791?v=4)
- [https://api.github.com/users/KoreaSecurity/events%7B/privacy%7D](https://api.github.com/users/KoreaSecurity/events%7B/privacy%7D)

## Related threats

- [Kyverno authorization bypass in generate rule validation](https://junglewise.ai/threats/cve-2026-124441-kyverno-before-1-19-2-contains-an-authorization-bypass)
- [Kyverno apiCall authorization bypass in namespace clamp](https://junglewise.ai/threats/cve-2026-124440-kyverno-from-1-19-1-before-1-19-2-contains-an-authorization)
- [Kyverno unbounded decompression in notary signature fetch](https://junglewise.ai/threats/cve-2026-122323-kyverno-from-1-11-0-before-1-19-2-contains-an-unbounded)
- [Kyverno verifyImages signature verification bypass via cache](https://junglewise.ai/threats/cve-2026-122321-kyverno-1-18-0-before-1-19-2-contains-a-signature-verification)
- [Kyverno missing authorization in generate.clone namespace](https://junglewise.ai/threats/cve-2026-122320-kyverno-before-1-19-2-contains-a-missing-authorization)