Skip to main content
CVE-2026-122316VulnerabilityPublished

Kyverno from 1.17.0 before 1.19.2 contains a missing authorization vulnerability in the mutate-existing background

Affects kyvernoSource GCVE Database

0
Compare
Authoritative record:CVE-2026-122316· High 8.4

Not known to be exploited · CVSS 8.4 High : upgrade to 1.19.2 soon.

Data as of 5 Nov 2026, 04:14 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.4
CNA (VulnCheck)CVSS 3.18.5
Patch
Available – fixed in 1.19.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:L/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade kyverno/kyverno to 1.19.2.

Affected software

ProductAffectedFixed in
GitHubkyverno/kyvernopkg:github/kyverno/kyvernoOther threatsAffected
  • >=1.17.0 <1.19.2
Fixed in
  • 1.19.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Kyverno version 1.19.2 and later. Users should upgrade to version 1.19.2 or newer to remediate this vulnerability. No other mitigation or temporary workaround is indicated.

Description

Kyverno versions from 1.17.0 up to but not including 1.19.2 have a missing authorization vulnerability in the mutate-existing background processor. This flaw allows namespaced tenants to modify resources outside their own namespace by creating a NamespacedMutatingPolicy targeting Namespace objects or resources in other namespaces. Exploitation can lead to the background-controller ServiceAccount stripping Pod Security labels cluster-wide.

References

Community reviews

Loading reviews…