CVE-2026-41323: Kyverno is a policy engine designed for cloud native platform engineering teams

This month

HIGH 8.1UPGRADE

CVE-2026-41323 is a high-severity flaw (CVSS 8.1) affecting kyverno. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 configura

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 54%)
CISA exploited list	No
Weakness	CWE-200, CWE-918
Published	2026-04-24
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: kyverno

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-24 04:16 UTCPublished CVE record published
2026-06-17 10:46 UTCUpdated Record last modified

kyverno kyverno UPGRADE

Affected: < 1.16.4 · >= 1.17.0 and < 1.17.2

Fixed in: 1.16.4, 1.17.2

Safe to downgrade to: a release before 1.17.0

1. Check installed version

apt-cache policy kyverno || rpm -q kyverno || kyverno --version

2. UPGRADE to 1.16.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kyverno

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kyverno

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.17.0 (Debian / Ubuntu)

apt-cache madison kyverno sudo apt install kyverno=<VERSION_BEFORE_1.17.0> sudo apt-mark hold kyverno

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list kyverno sudo dnf downgrade kyverno-<VERSION_BEFORE_1.17.0> sudo dnf versionlock add kyverno

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41323?

kyverno: upgrade to 1.16.4, 1.17.2. Exact commands for each OS are on this page.

Is CVE-2026-41323 being exploited?

CVE-2026-41323 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41323 affect?

CVE-2026-41323 affects kyverno. Severity is high (CVSS 8.1). 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 ServiceAccou

How urgent is CVE-2026-41323?

Priority 45/100. High severity; Public exploit reference

Related CVEs

CVE-2026-41485 HIGH 7.7 UPGRADE Kyverno is a policy engine designed for cloud native platform engineering teams
CVE-2026-41068 HIGH 7.7 UPGRADE Kyverno is a policy engine designed for cloud native platform engineering teams
CVE-2026-40868 HIGH 8.1 UPGRADE Kyverno is a policy engine designed for cloud native platform engineering teams

References

← Back to latest CVEs