Is CVE-2026-122318 exploited in the wild?

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

How severe is CVE-2026-122318?

High severity, with a CVSS score of 7.7, published 5 November 2026.

Is there a fix for CVE-2026-122318?

Yes: fixed in 1.19.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-122318 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-122318?

Check whether you run 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-122318: Kyverno authentication bypass in certificate verification

CVE-2026-122318 · Severity: high · CVSS 7.7 · Published 2026-11-05

Kyverno is a policy engine that validates container image signatures to ensure they come from trusted signers. A flaw in certificate validation allows attackers with access to a private certificate authority to forge image signatures that bypass signer identity checks, potentially allowing unauthorized or malicious container images to be deployed.

Technologies: Kyverno. Vendors: Kyverno.

Quick answers

Is CVE-2026-122318 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-122318 being exploited in the wild.
How severe is CVE-2026-122318?: High severity, with a CVSS score of 7.7, published 5 November 2026.
Which products and versions are affected?: Kyverno before 1.19.2.
Is there a fix for CVE-2026-122318?: Yes: fixed in 1.19.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-122318 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-122318?: Check whether you run 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

Fixed in: 1.19.2

Technical details

The vulnerability is in the matchCertificateData function in pkg/image/verifiers/cpol/cosign/cosign.go. When a verifyImages policy pins an image signer by subject identity (subject or subjectRegExp), the check is incorrectly skipped if the signing certificate lacks a Subject Alternative Name (SAN) extension. An attacker with a leaf certificate from a configured private trust root can omit the SAN, set the required Fulcio issuer OID, and sign malicious images that bypass the identity pin while still passing the issuer check. The vulnerability requires prior compromise or access to the private PKI and affects non-keyless attestor configurations only.

Affected products

Kyverno Kyverno before 1.19.2

Timeline

2026-10-21: disclosed
2026-11-05: advisory

References

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