Home › Vulnerabilities

Kyverno Flaw CVE-2026-122321: Update Now

Published November 5, 2026 · Last updated November 5, 2026

CVE Critical Patch

The short version: CVE-2026-122321 is a critical-severity security flaw in Kyverno. The National Vulnerability Database (NVD) published it on November 5, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 5, 2026, CISA had not added CVE-2026-122321 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-122321

The record was filed by vulncheck.com. In its own words: "Kyverno 1.18.0 before 1.19.2 contains a signature verification bypass in verifyImages because cached verification results are keyed by the image reference string (such as a tag) rather than bound to the verified digest, so cache hits skip signature and attestation checks. An attacker who can submit workloads and move a registry tag can warm the cache with a signed image, repoint the tag, and have Kyverno admit the workload and use mutateDigest to pin the unverified digest."

Why Kyverno admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on vulncheck.com rated CVE-2026-122321 9.1 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is low, to keeping data unaltered is high, and to keeping Kyverno running is low. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L.

Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, the address listed on vulncheck.com gives it 8.5 (High, CVSS 4.0).

Affected Kyverno releases

According to the record, these releases are vulnerable:

  • 1.18.0 up to, but not including, 1.19.2

The type of bug behind CVE-2026-122321

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-367, Time-of-check Time-of-use (TOCTOU) Race Condition. MITRE describes this class of bug as follows: "The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check."

Vendor remediation for CVE-2026-122321

The vendor advisory remediation for operators of Kyverno, quoted for this page, is: "Upgrade every Kyverno installation running 1.18.0 through 1.19.1 to release 1.19.2 or newer; the project's GitHub security advisory GHSA-2r43-6962-xcw5 names it as the fixed version. Platform teams that rely on the verifyImages rule to enforce signed container images should act first. After upgrading, restart the admission controller so stale cached results are dropped, then review which workloads were admitted since the vulnerable release and compare their running image digests against the signed ones. Until then, pin images by digest in manifests instead of by tag, and restrict who can push or move tags in your registry."

What to do about it

  • Update now: Upgrade every Kyverno installation running 1.18.0 through 1.19.1 to release 1.19.2 or newer; the project's GitHub security advisory GHSA-2r43-6962-xcw5 names it as the fixed version. Platform teams that rely on the verifyImages rule to enforce signed container images should act first. After upgrading, restart the admission controller so stale cached results are dropped, then review which workloads were admitted since the vulnerable release and compare their running image digests against the signed ones. Until then, pin images by digest in manifests instead of by tag, and restrict who can push or move tags in your registry.
  • Who should act: IT teams, managed service providers, and developers who run or ship Kyverno. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Kyverno (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 5, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-122321. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-122321 record details from CISA and NVD

  • Attack complexity for CVE-2026-122321: low
  • CVE-2026-122321 CVSS scope: changed
  • NVD sub-scores for CVE-2026-122321: exploitability 3.1, impact 5.3.
  • Who mapped the weakness type: the address listed on vulncheck.com (Primary)
  • References in the NVD record: 2.

Dates to know

  • November 5, 2026: NVD publishes CVE-2026-122321.
  • November 5, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-122321 is not listed.
  • November 5, 2026: most recent NVD update (record status: Received).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.