Kyverno CVEs: open source vs Nirmata Enterprise for Kyverno
Across Kyverno 1.14 to 1.19, the latest open source images carry 362 critical and high CVEs. The matching Nirmata Enterprise for Kyverno images carry 63. Both sides are scanned with Trivy and Grype on the same day; last scan October 28, 2026.
Critical and high CVEs by release
362CVEs in Kyverno open source
63CVEs in Nirmata Enterprise for Kyverno
83%fewer, across Kyverno 1.14 to 1.19
| Release | Open source vs N4K | Reduction |
|---|---|---|
| 1.19 | Open source: 2 N4K: 1 | 50%fewer |
| 1.18 | Open source: 44 N4K: 1 | 98%fewer |
| 1.17 | Open source: 66 N4K: 2 | 97%fewer |
| 1.16 | Open source: 72 N4K: 18 | 75%fewer |
| 1.15 | Open source: 91 N4K: 19 | 79%fewer |
| 1.14 | Open source: 87 N4K: 22 | 75%fewer |
Latest image of each release, scanned the same day. Hover a bar for the image tag, severity split and publish date; the per-release detail is under every finding.
Where the CVEs are
Each finding is grouped by where it lives: Kyverno's own code, the Go standard library it is compiled with, its Go dependencies, or the base image. Figures are open source → N4K.
| Release | Kyverno code | Go standard library | Go dependencies | Total |
|---|---|---|---|---|
| 1.19 | 0 → see note* | 1 → 0 | 1 → 1 | 2 → 1 |
| 1.18 | 0 → see note* | 20 → 0 | 24 → 1 | 44 → 1 |
| 1.17 | 0 → see note* | 26 → 0 | 40 → 1 | 66 → 2 |
| 1.16 | 6 → see note* | 26 → 11 | 40 → 7 | 72 → 18 |
| 1.15 | 7 → see note* | 33 → 11 | 51 → 8 | 91 → 19 |
| 1.14 | 0 → see note* | 37 → 11 | 50 → 11 | 87 → 22 |
* Scanners match Kyverno's own code by version number, which doesn't work reliably for N4K builds, so N4K figures for Kyverno code aren't shown. The fixes in each N4K build are listed in the release notes. Totals are the scanners' counts.
CVEs in Kyverno's own code
Hardened and minimal image providers rebuild open source Kyverno on a clean base and newer dependencies. That removes OS and library CVEs. A vulnerability in Kyverno's own code stays until the code is fixed, and on an older release that takes a backport. Open source Kyverno backports fixes to at most one prior minor release; Nirmata Enterprise for Kyverno backports them to the current release and the four before it.
Image scanners can't confirm these fixes in N4K builds, so the status below is verified against the code on each release branch rather than read from scan results. Each Kyverno advisory, with its affected and fixed open source versions, is on Kyverno CVEs and security advisories; the fixes in each N4K build are in the release notes.
- Kyverno 1.19: 40 fixed, 2 open
- Kyverno 1.18: 29 fixed, 13 open
- Kyverno 1.17: 29 fixed, 13 open
- Kyverno 1.16: 29 fixed, 10 open
- Kyverno 1.15: 22 fixed, 15 open
- Kyverno 1.14: 25 fixed, 12 open
| Advisory | 1.19 | 1.18 | 1.17 | 1.16 | 1.15 | 1.14 |
|---|---|---|---|---|---|---|
| CVE-2026-40868apiCall attaches the Kyverno ServiceAccount token to any policy-controlled service URL by default | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.0-n4k.nirmata.3 | Fixedv1.16.3-n4k.nirmata.9 | Open | Fixedv1.14.4-n4k.nirmata.7 |
| CVE-2026-41068The ConfigMap context loader resolves a ConfigMap in any namespace without checking the policy's own | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.2-n4k.nirmata.1 | Fixedv1.16.3-n4k.nirmata.9 | Open | Open |
| CVE-2026-41323apiCall ServiceAccount token attachment, reported separately from CVE-2026-40868 | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.0-n4k.nirmata.3 | Fixedv1.16.3-n4k.nirmata.9 | Open | Fixedv1.14.4-n4k.nirmata.7 |
| CVE-2026-41485A nil patchesJson6902 after variable substitution panics the mutate engine through a bare type assertion | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.2-n4k.nirmata.1 | Fixedv1.16.3-n4k.nirmata.9 | Open | Open |
| CVE-2026-4789CEL http.Get and http.Post reachable through NamespacedValidatingPolicy | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.0-n4k.nirmata.3 | Fixedv1.16.3-n4k.nirmata.9 | Not affected | Not affected |
| GHSA-24cc-9745-hxfcUnchecked type assertions on remote attestation and OCI manifest JSON panicked on a non-string type field, bypassing image verification and crash-looping the reports controller. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-2r43-6962-xcw5The image verification cache keyed a prior pass verdict on the image reference string, which could be a bare tag. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-338x-hgrv-626hVariable substitution re-scanned already-substituted text, so nested or self-referential values could drive unbounded re-scanning. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-3f2c-hfj8-542wNotary attestation statement extraction checked the compressed descriptor and layer size against the 10 MB payload limit but read the decompressed predicate into memory without a bound, so an attacker-supplied referrer artifact that compresses small and expands large could exhaust admission controller memory. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-3xfv-vq8x-qhg4A namespaced Policy apiCall validated the urlPath against the whole string, query and fragment included, but executed only the parsed path, so validation and execution disagreed on the target. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-493q-9xvg-9xf3Namespaced legacy generate policies could access clone sources outside their namespace when evaluated witho... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-4pqm-wqq6-h9q2Namespaced CEL policy helpers (resource.get, resource.list, and resource.post) passed their resource, group, and version arguments to the Kubernetes dynamic client, which builds the request path by joining segments. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-57hf-r692-6vrxNamespaced Policy globalReference access remains rejected at both admission and runtime | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-59v6-2x73-wfg4A policy scoped to a single namespace could read the full contents of a cluster-scoped GlobalContextEntry through a globalReference context entry, including data cached from namespaces the policy's tenant has no permission to read. | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-5cjf-wwfg-pj4cThe ImageValidatingPolicy evaluator ignored a PolicyException's spec.images and spec.allowedValues fields. | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Not affected | Not affected |
| GHSA-5qq8-67g6-4h2wA namespaced Policy's apiCall urlPath was clamped to the policy's own namespace by normalising the path before comparing it, but the normalisation did not decode percent-encoded characters. | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-68v8-7j3j-8995CEL HTTP destination checks could treat alternate address encodings differently from their canonical destin... | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.16 | Fixedv1.16.3-n4k.nirmata.14 | Fixedv1.15.2-n4k.nirmata.12 | Fixedv1.14.4-n4k.nirmata.7 |
| GHSA-8mrj-27wr-599gThe wildcard glob matcher used a recursive algorithm whose running time could grow exponentially with pattern length, so a crafted policy or resource string could stall policy evaluation. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-8wfp-579w-6r25apiCall forwards the raw, default-audience ServiceAccount token because the scoped-token change was never backported | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.1 | Fixedv1.17.0-n4k.nirmata.3 | Fixedv1.16.3-n4k.nirmata.9 | Open | Fixedv1.14.4-n4k.nirmata.7 |
| GHSA-c5qq-7g2q-cpqpA namespaced Policy's apiCall urlPath was clamped to the policy's own namespace by normalising the path before comparing it, but the normalisation did not decode percent-encoded characters. | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-f5c5-qwxq-xg9rNamespaced Policy named and selector-based CEL parameter references default to and remain within the policy... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-f96w-622v-rqpqA namespaced MutatingPolicy's mutate-existing CEL target expression was trusted without confinement, so it... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Not affected | Not affected | Not affected |
| GHSA-fcfr-fr8g-qjqvA cosign signing certificate with no subject alternative name caused the configured subject and subjectRegExp identity check to be skipped rather than failing, so a certificate carrying no identity satisfied a policy that pinned one. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-fmqp-4wfc-w3v7apiCall can reach in-cluster Services, reading another tenant's data through a ClusterIP | Open | Open | Open | Open | Open | Open |
| GHSA-fr24-3hvf-393qNotary signature blob fetching applied the same compressed-only size check and buffered the decompressed signature layer without a bound, giving the same memory-exhaustion path during image verification. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-gghj-wcpm-cchrPolicy-controlled registry and Sigstore HTTP destinations now share an egress guard that validates every re... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-gm4r-g7rh-3pjjNamespace confinement now covers legacy Policy imageRegistry context and verifyImages credentials, Namespac... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-h3pm-q9ww-f439The validating webhook trusted the verify-images annotation written by the mutating webhook, so a request that set the annotation directly, or replayed it on UPDATE, was admitted without verification. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-hg5v-hwm3-956rController-issued HMAC provenance binds persisted target and policy UIDs to generation routing metadata | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-jcw5-3wcg-fqx5A namespaced MutatingPolicy's mutate-existing targets could redirect a write to a resource in another names... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Not affected | Not affected | Not affected |
| GHSA-m8p2-qqmx-j53xCEL policy expressions were compiled without a cost limit, so the work one expression could do was unbounded and a policy author could exhaust a shared controller. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-p58h-r4j3-h5vxThe cleanup controller built its context loader without the policy's own scope, so a namespaced CleanupPolicy's context entries were treated as cluster scoped and were not confined to the policy's namespace. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-pcx2-xcq4-65vfThe same validate/execute divergence in a namespaced Policy apiCall urlPath let a query- or fragment-hidden decoy namespace segment pass the namespace clamp while the request read resources in a different namespace as the Kyverno ServiceAccount. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-q62c-r9v2-cf64Legacy generate and cleanup policy admission checked Kyverno controller permissions without independently a... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-q825-p383-r9v5The legacy apiCall service executor and the GlobalContextEntry external-API path skipped the SSRF host/CIDR... | Fixedv1.19.0-n4k.nirmata.1 | Fixedv1.18.0-n4k.nirmata.3 | Fixedv1.17.2-n4k.nirmata.16 | Fixedv1.16.3-n4k.nirmata.14 | Fixedv1.15.2-n4k.nirmata.12 | Fixedv1.14.4-n4k.nirmata.7 |
| GHSA-qc9c-3fgf-cgq8The ValidatingAdmissionPolicy generator folded PolicyExceptions into generated policies without applying the gates runtime enforcement uses, so an exception the engine would reject still took effect in the generated native policy. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-qr4g-8hrp-c4rwapiCall SSRF to internal destinations; the metadata and loopback variants are blocked but in-cluster Service addresses are not | Open | Open | Open | Open | Open | Open |
| GHSA-r2p2-3892-5jjfAn unchecked type assertion in the In and NotIn operators could panic on a non-string key element. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-rcxg-3f92-3mgrA namespaced CleanupPolicy could issue apiCall context requests to paths outside its own namespace. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
| GHSA-vjfx-fp68-rh4vLegacy namespaced generate rules allowed expressions to select resource types or namespaces before their sc... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Open | Open | Open |
| GHSA-vm98-8c25-h274A namespaced MutatingPolicy's mutate-existing resource-rule targets were not confined to the policy's names... | Fixedv1.19.0-n4k.nirmata.2 | Open | Open | Not affected | Not affected | Not affected |
| GHSA-x4xq-p8g4-6fwgAn unchecked type assertion to string on a substituted or admission-supplied value could panic the engine or the policy-validation webhook. | Fixedv1.19.0-n4k.nirmata.2 | Fixedv1.18.0-n4k.nirmata.7 | Fixedv1.17.2-n4k.nirmata.22 | Fixedv1.16.3-n4k.nirmata.17 | Fixedv1.15.2-n4k.nirmata.15 | Fixedv1.14.4-n4k.nirmata.8 |
Fixed names the N4K build carrying the fix. Not affected means the vulnerable code never shipped in that release. Open means it is still present. Each verdict is checked against the code on that release branch.
Nirmata Enterprise for Kyverno is also available through Chainguard Commercial Builds: Kyverno code fixes from the maintainers, on a hardened, zero- to low-CVE base.
Every finding, by release
Each critical and high CVE in the open source images, and whether the scanners still find it in the matching N4K image.
Kyverno 1.19: 2 in v1.19.2, 1 in v1.19.0-n4k.nirmata.3
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.1.4 | v4.1.4 | 4.1.6 |
| CVE-2026-111943 | High | stdlib | v1.26.9 | Not found in scan | 1.26.10, 1.27.3 |
Kyverno 1.18: 44 in v1.18.2, 1 in v1.18.0-n4k.nirmata.8
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-78663 | Critical | golang.org/x/net | v0.56.0 | Not found in scan | 0.60.0 |
| CVE-2026-78663 | Critical | stdlib | go1.26.4 | Not found in scan | 1.26.9 |
| CVE-2026-44973 | High | github.com/go-git/go-billy/v5 | v5.8.0 | Not found in scan | 5.9.0 |
| CVE-2026-45022 | High | github.com/go-git/go-git/v5 | v5.18.0 | Not found in scan | 5.19.0 |
| CVE-2026-71556 | High | github.com/go-git/go-git/v5 | v5.18.0 | Not found in scan | 5.19.2 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.1.4 | v4.1.4 | 4.1.6 |
| CVE-2026-63209 | High | github.com/klauspost/compress | v1.18.5 | Not found in scan | 1.18.7 |
| CVE-2026-49478 | High | github.com/sigstore/fulcio | v1.8.5 | Not found in scan | 1.8.6 |
| CVE-2026-56854 | High | golang.org/x/crypto | v0.53.0 | Not found in scan | 0.55.0 |
| CVE-2026-56855 | High | golang.org/x/crypto | v0.53.0 | Not found in scan | 0.56.0 |
| CVE-2026-78662 | High | golang.org/x/crypto | v0.53.0 | Not found in scan | 0.56.0 |
| CVE-2026-56864 | High | golang.org/x/mod | v0.36.0 | Not found in scan | 0.40.0 |
| CVE-2026-56865 | High | golang.org/x/mod | v0.36.0 | Not found in scan | 0.40.0 |
| CVE-2026-78659 | High | golang.org/x/net | v0.56.0 | Not found in scan | 0.60.0 |
| CVE-2026-78660 | High | golang.org/x/net | v0.56.0 | Not found in scan | 0.60.0 |
| CVE-2026-78669 | High | golang.org/x/net | v0.56.0 | Not found in scan | 0.60.0 |
| CVE-2026-97032 | High | golang.org/x/net | v0.56.0 | Not found in scan | 0.60.0 |
| CVE-2026-56851 | High | golang.org/x/text | v0.38.0 | Not found in scan | 0.41.0 |
| CVE-2026-56852 | High | golang.org/x/text | v0.38.0 | Not found in scan | 0.39.0 |
| CVE-2026-84304 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.83.1 |
| CVE-2026-84445 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.1 |
| CVE-2026-50151 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.1 |
| CVE-2026-50163 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-85731 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-111943 | High | stdlib | v1.26.4 | Not found in scan | 1.26.10, 1.27.3 |
| CVE-2026-33818 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39821 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39822 | High | stdlib | v1.26.4 | Not found in scan | 1.25.12, 1.26.5, 1.27.0-rc.2 |
| CVE-2026-46600 | High | stdlib | v1.26.4 | Not found in scan | 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56853 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56858 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56859 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56860 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56862 | High | stdlib | v1.26.4 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56866 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-78659 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9 |
| CVE-2026-78660 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9 |
| CVE-2026-78667 | High | stdlib | v1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-78669 | High | stdlib | v1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-94439 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-94440 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-97031 | High | stdlib | v1.26.4 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-97032 | High | stdlib | go1.26.4 | Not found in scan | 1.26.9 |
Kyverno 1.17: 66 in v1.17.2, 2 in v1.17.2-n4k.nirmata.24
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-39830 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39831 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39832 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39834 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-42508 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-78663 | Critical | golang.org/x/net | v0.52.0 | Not found in scan | 0.60.0 |
| CVE-2026-78663 | Critical | stdlib | go1.25.9 | Not found in scan | 1.26.9 |
| CVE-2026-44973 | High | github.com/go-git/go-billy/v5 | v5.8.0 | Not found in scan | 5.9.0 |
| CVE-2026-45022 | High | github.com/go-git/go-git/v5 | v5.17.2 | Not found in scan | 5.19.0 |
| CVE-2026-71556 | High | github.com/go-git/go-git/v5 | v5.17.2 | Not found in scan | 5.19.2 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.1.4 | v4.1.4 | 4.1.6 |
| CVE-2026-63209 | High | github.com/klauspost/compress | v1.18.4 | Not found in scan | 1.18.7 |
| CVE-2026-41485 | High | github.com/kyverno/kyverno | – | v1.17.2-n4k.nirmata.24 | 1.16.4, 1.17.2 |
| CVE-2026-49478 | High | github.com/sigstore/fulcio | v1.8.5 | Not found in scan | 1.8.6 |
| CVE-2026-48702 | High | github.com/sigstore/rekor | v1.5.0 | Not found in scan | 1.5.2 |
| CVE-2026-39828 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39829 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39835 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-46595 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-46597 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-56854 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.55.0 |
| CVE-2026-56855 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.56.0 |
| CVE-2026-78662 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.56.0 |
| CVE-2026-56864 | High | golang.org/x/mod | v0.33.0 | Not found in scan | 0.40.0 |
| CVE-2026-56865 | High | golang.org/x/mod | v0.33.0 | Not found in scan | 0.40.0 |
| CVE-2026-25681 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-27136 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-33814 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.53.0 |
| CVE-2026-39821 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-46600 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.56.0 |
| CVE-2026-78659 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.60.0 |
| CVE-2026-78660 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.60.0 |
| CVE-2026-78669 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.60.0 |
| CVE-2026-97032 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.60.0 |
| CVE-2026-56851 | High | golang.org/x/text | v0.35.0 | Not found in scan | 0.41.0 |
| CVE-2026-56852 | High | golang.org/x/text | v0.35.0 | Not found in scan | 0.39.0 |
| CVE-2026-84304 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.83.1 |
| CVE-2026-84445 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.1 |
| CVE-2026-50151 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.1 |
| CVE-2026-50163 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-85731 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-111943 | High | stdlib | v1.25.9 | Not found in scan | 1.26.10, 1.27.3 |
| CVE-2026-27145 | High | stdlib | v1.25.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-33811 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33814 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33818 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39820 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-39821 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39822 | High | stdlib | v1.25.9 | Not found in scan | 1.25.12, 1.26.5, 1.27.0-rc.2 |
| CVE-2026-39836 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42499 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42504 | High | stdlib | v1.25.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-56853 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56858 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56859 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56860 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56862 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56866 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-78659 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9 |
| CVE-2026-78660 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9 |
| CVE-2026-78667 | High | stdlib | v1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-78669 | High | stdlib | v1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-94439 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-94440 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-97031 | High | stdlib | v1.25.9 | Not found in scan | 1.26.9, 1.27.2 |
| CVE-2026-97032 | High | stdlib | go1.25.9 | Not found in scan | 1.26.9 |
Kyverno 1.16: 72 in v1.16.4, 18 in v1.16.3-n4k.nirmata.17
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-39830 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39831 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39832 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39834 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-42508 | Critical | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-78663 | Critical | golang.org/x/net | v0.52.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78663 | Critical | stdlib | go1.25.9 | go1.26.6 | 1.26.9 |
| CVE-2026-44973 | High | github.com/go-git/go-billy/v5 | v5.8.0 | Not found in scan | 5.9.0 |
| CVE-2026-45022 | High | github.com/go-git/go-git/v5 | v5.17.2 | Not found in scan | 5.19.0 |
| CVE-2026-71556 | High | github.com/go-git/go-git/v5 | v5.17.2 | Not found in scan | 5.19.2 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.1.4 | v4.1.4 | 4.1.6 |
| CVE-2026-63209 | High | github.com/klauspost/compress | v1.18.1 | v1.18.6 | 1.18.7 |
| CVE-2026-40868 | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | 1.17.0 |
| CVE-2026-41068 | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | - |
| CVE-2026-41323 | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | 1.17.0 |
| CVE-2026-4789 | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | 1.17.0 |
| GHSA-8wfp-579w-6r25 | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | 1.17.0 |
| GHSA-qr4g-8hrp-c4rw | High | github.com/kyverno/kyverno | v1.16.4+dirty | See release notes | - |
| CVE-2026-49478 | High | github.com/sigstore/fulcio | v1.8.5 | Not found in scan | 1.8.6 |
| CVE-2026-48702 | High | github.com/sigstore/rekor | v1.5.1 | Not found in scan | 1.5.2 |
| CVE-2026-39828 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39829 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-39835 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-46595 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-46597 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.52.0 |
| CVE-2026-56854 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.55.0 |
| CVE-2026-56855 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.56.0 |
| CVE-2026-78662 | High | golang.org/x/crypto | v0.49.0 | Not found in scan | 0.56.0 |
| CVE-2026-56864 | High | golang.org/x/mod | v0.33.0 | Not found in scan | 0.40.0 |
| CVE-2026-56865 | High | golang.org/x/mod | v0.33.0 | Not found in scan | 0.40.0 |
| CVE-2026-25681 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-27136 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-33814 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.53.0 |
| CVE-2026-39821 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.55.0 |
| CVE-2026-46600 | High | golang.org/x/net | v0.52.0 | Not found in scan | 0.56.0 |
| CVE-2026-78659 | High | golang.org/x/net | v0.52.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78660 | High | golang.org/x/net | v0.52.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78669 | High | golang.org/x/net | v0.52.0 | v0.58.0 | 0.60.0 |
| CVE-2026-97032 | High | golang.org/x/net | v0.52.0 | v0.58.0 | 0.60.0 |
| CVE-2026-56851 | High | golang.org/x/text | v0.35.0 | Not found in scan | 0.41.0 |
| CVE-2026-56852 | High | golang.org/x/text | v0.35.0 | Not found in scan | 0.39.0 |
| CVE-2026-84304 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.83.1 |
| CVE-2026-84445 | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.80.0 | Not found in scan | 1.82.1 |
| CVE-2026-50151 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.1 |
| CVE-2026-50163 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-85731 | High | oras.land/oras-go/v2 | v2.6.0 | Not found in scan | 2.6.2 |
| CVE-2026-111943 | High | stdlib | v1.25.9 | v1.26.6 | 1.26.10, 1.27.3 |
| CVE-2026-27145 | High | stdlib | v1.25.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-33811 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33814 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33818 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39820 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-39821 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39822 | High | stdlib | v1.25.9 | Not found in scan | 1.25.12, 1.26.5, 1.27.0-rc.2 |
| CVE-2026-39836 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42499 | High | stdlib | v1.25.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42504 | High | stdlib | v1.25.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-56853 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56858 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56859 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56860 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56862 | High | stdlib | v1.25.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56866 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-78659 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9 |
| CVE-2026-78660 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9 |
| CVE-2026-78667 | High | stdlib | v1.25.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-78669 | High | stdlib | v1.25.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-94439 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-94440 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-97031 | High | stdlib | v1.25.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-97032 | High | stdlib | go1.25.9 | go1.26.6 | 1.26.9 |
Kyverno 1.15: 91 in v1.15.3, 19 in v1.15.2-n4k.nirmata.15
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-39830 | Critical | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-39831 | Critical | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-39832 | Critical | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-39834 | Critical | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-42508 | Critical | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-78663 | Critical | golang.org/x/net | v0.41.0 | v0.58.0 | 0.60.0 |
| CVE-2026-33186 | Critical | google.golang.org/grpc | v1.73.0 | Not found in scan | 1.79.3 |
| CVE-2025-68121 | Critical | stdlib | v1.24.9 | Not found in scan | 1.24.13, 1.25.7, 1.26.0-rc.3 |
| CVE-2026-78663 | Critical | stdlib | go1.24.9 | go1.26.6 | 1.26.9 |
| CVE-2025-15558 | High | github.com/docker/cli | v27.5.0+incompatible | Not found in scan | 29.2.0 |
| CVE-2026-44973 | High | github.com/go-git/go-billy/v5 | v5.6.2 | Not found in scan | 5.9.0 |
| CVE-2026-45022 | High | github.com/go-git/go-git/v5 | v5.16.2 | Not found in scan | 5.19.0 |
| CVE-2026-71556 | High | github.com/go-git/go-git/v5 | v5.16.2 | Not found in scan | 5.19.2 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v3 | v3.0.4 | v3.0.5 | - |
| CVE-2026-34986 | High | github.com/go-jose/go-jose/v3 | v3.0.4 | Not found in scan | 3.0.5 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.0.5 | v4.1.4 | 4.1.6 |
| CVE-2026-34986 | High | github.com/go-jose/go-jose/v4 | v4.0.5 | Not found in scan | 4.1.4 |
| CVE-2026-63209 | High | github.com/klauspost/compress | v1.18.0 | v1.18.6 | 1.18.7 |
| CVE-2026-40868 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | 1.17.0 |
| CVE-2026-41068 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | - |
| CVE-2026-41323 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | 1.17.0 |
| CVE-2026-41485 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | 1.16.4, 1.17.2 |
| GHSA-8wfp-579w-6r25 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | 1.17.0 |
| GHSA-fmqp-4wfc-w3v7 | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | 1.16.2 |
| GHSA-qr4g-8hrp-c4rw | High | github.com/kyverno/kyverno | v1.15.3+dirty | See release notes | - |
| CVE-2025-66506 | High | github.com/sigstore/fulcio | v1.6.6 | Not found in scan | 1.8.3 |
| CVE-2026-49478 | High | github.com/sigstore/fulcio | v1.6.6 | Not found in scan | 1.8.6 |
| CVE-2026-48702 | High | github.com/sigstore/rekor | v1.3.10 | Not found in scan | 1.5.2 |
| CVE-2025-66564 | High | github.com/sigstore/timestamp-authority | v1.2.4 | Not found in scan | 2.0.3 |
| CVE-2026-29181 | High | go.opentelemetry.io/otel | v1.37.0 | Not found in scan | 1.41.0 |
| CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.37.0 | Not found in scan | 1.40.0 |
| CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.37.0 | Not found in scan | 1.43.0 |
| CVE-2025-47913 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.43.0 |
| CVE-2026-39828 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-39829 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-39835 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-46595 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-46597 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.52.0 |
| CVE-2026-56854 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.55.0 |
| CVE-2026-56855 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.56.0 |
| CVE-2026-78662 | High | golang.org/x/crypto | v0.39.0 | Not found in scan | 0.56.0 |
| CVE-2026-56864 | High | golang.org/x/mod | v0.25.0 | Not found in scan | 0.40.0 |
| CVE-2026-56865 | High | golang.org/x/mod | v0.25.0 | Not found in scan | 0.40.0 |
| CVE-2026-25681 | High | golang.org/x/net | v0.41.0 | Not found in scan | 0.55.0 |
| CVE-2026-27136 | High | golang.org/x/net | v0.41.0 | Not found in scan | 0.55.0 |
| CVE-2026-33814 | High | golang.org/x/net | v0.41.0 | Not found in scan | 0.53.0 |
| CVE-2026-39821 | High | golang.org/x/net | v0.41.0 | Not found in scan | 0.55.0 |
| CVE-2026-46600 | High | golang.org/x/net | v0.41.0 | Not found in scan | 0.56.0 |
| CVE-2026-78659 | High | golang.org/x/net | v0.41.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78660 | High | golang.org/x/net | v0.41.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78669 | High | golang.org/x/net | v0.41.0 | v0.58.0 | 0.60.0 |
| CVE-2026-97032 | High | golang.org/x/net | v0.41.0 | v0.58.0 | 0.60.0 |
| CVE-2026-56851 | High | golang.org/x/text | v0.26.0 | Not found in scan | 0.41.0 |
| CVE-2026-56852 | High | golang.org/x/text | v0.26.0 | Not found in scan | 0.39.0 |
| CVE-2026-84304 | High | google.golang.org/grpc | v1.73.0 | Not found in scan | 1.83.1 |
| CVE-2026-84445 | High | google.golang.org/grpc | v1.73.0 | Not found in scan | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.73.0 | Not found in scan | 1.82.1 |
| CVE-2026-50151 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.1 |
| CVE-2026-50163 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.2 |
| CVE-2026-85731 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.2 |
| CVE-2025-61726 | High | stdlib | v1.24.9 | Not found in scan | 1.24.12, 1.25.6 |
| CVE-2025-61729 | High | stdlib | v1.24.9 | Not found in scan | 1.24.11, 1.25.5 |
| CVE-2026-111943 | High | stdlib | v1.24.9 | v1.26.6 | 1.26.10, 1.27.3 |
| CVE-2026-25679 | High | stdlib | v1.24.9 | Not found in scan | 1.25.8, 1.26.1 |
| CVE-2026-27145 | High | stdlib | v1.24.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-32280 | High | stdlib | v1.24.9 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-32281 | High | stdlib | v1.24.9 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-32283 | High | stdlib | v1.24.9 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-33811 | High | stdlib | v1.24.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33814 | High | stdlib | v1.24.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33818 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39820 | High | stdlib | v1.24.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-39821 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39822 | High | stdlib | v1.24.9 | Not found in scan | 1.25.12, 1.26.5, 1.27.0-rc.2 |
| CVE-2026-39836 | High | stdlib | v1.24.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42499 | High | stdlib | v1.24.9 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42504 | High | stdlib | v1.24.9 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-56853 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56858 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56859 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56860 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56862 | High | stdlib | v1.24.9 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56866 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-78659 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9 |
| CVE-2026-78660 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9 |
| CVE-2026-78667 | High | stdlib | v1.24.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-78669 | High | stdlib | v1.24.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-94439 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-94440 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-97031 | High | stdlib | v1.24.9 | v1.26.6 | 1.26.9, 1.27.2 |
| CVE-2026-97032 | High | stdlib | go1.24.9 | go1.26.6 | 1.26.9 |
Kyverno 1.14: 87 in v1.14.5, 22 in v1.14.4-n4k.nirmata.8
| CVE | Severity | Package | Open source | N4K | Fixed in |
|---|---|---|---|---|---|
| CVE-2026-39830 | Critical | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-39831 | Critical | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-39832 | Critical | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-39834 | Critical | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-42508 | Critical | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-78663 | Critical | golang.org/x/net | v0.38.0 | v0.58.0 | 0.60.0 |
| CVE-2026-33186 | Critical | google.golang.org/grpc | v1.71.1 | Not found in scan | 1.79.3 |
| CVE-2025-68121 | Critical | stdlib | v1.23.12 | Not found in scan | 1.24.13, 1.25.7, 1.26.0-rc.3 |
| CVE-2026-78663 | Critical | stdlib | go1.23.12 | go1.25.13 | 1.26.9 |
| CVE-2025-15558 | High | github.com/docker/cli | v27.5.0+incompatible | Not found in scan | 29.2.0 |
| CVE-2026-44973 | High | github.com/go-git/go-billy/v5 | v5.6.2 | Not found in scan | 5.9.0 |
| CVE-2026-45022 | High | github.com/go-git/go-git/v5 | v5.14.0 | Not found in scan | 5.19.0 |
| CVE-2026-71556 | High | github.com/go-git/go-git/v5 | v5.14.0 | Not found in scan | 5.19.2 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v3 | v3.0.4 | v3.0.5 | - |
| CVE-2026-34986 | High | github.com/go-jose/go-jose/v3 | v3.0.4 | Not found in scan | 3.0.5 |
| CVE-2026-116587 | High | github.com/go-jose/go-jose/v4 | v4.0.5 | v4.1.4 | 4.1.6 |
| CVE-2026-34986 | High | github.com/go-jose/go-jose/v4 | v4.0.5 | Not found in scan | 4.1.4 |
| CVE-2026-63209 | High | github.com/klauspost/compress | v1.18.0 | v1.18.6 | 1.18.7 |
| CVE-2025-66506 | High | github.com/sigstore/fulcio | v1.6.6 | Not found in scan | 1.8.3 |
| CVE-2026-49478 | High | github.com/sigstore/fulcio | v1.6.6 | v1.8.5 | 1.8.6 |
| CVE-2026-48702 | High | github.com/sigstore/rekor | v1.3.9 | Not found in scan | 1.5.2 |
| CVE-2025-66564 | High | github.com/sigstore/timestamp-authority | v1.2.4 | Not found in scan | 2.0.3 |
| CVE-2026-24051 | High | go.opentelemetry.io/otel/sdk | v1.35.0 | Not found in scan | 1.40.0 |
| CVE-2026-39883 | High | go.opentelemetry.io/otel/sdk | v1.35.0 | Not found in scan | 1.43.0 |
| CVE-2025-47913 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.43.0 |
| CVE-2026-39828 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-39829 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-39835 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-46595 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-46597 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.52.0 |
| CVE-2026-56854 | High | golang.org/x/crypto | v0.36.0 | Not found in scan | 0.55.0 |
| CVE-2026-56855 | High | golang.org/x/crypto | v0.36.0 | v0.55.0 | 0.56.0 |
| CVE-2026-78662 | High | golang.org/x/crypto | v0.36.0 | v0.55.0 | 0.56.0 |
| CVE-2026-56864 | High | golang.org/x/mod | v0.24.0 | Not found in scan | 0.40.0 |
| CVE-2026-56865 | High | golang.org/x/mod | v0.24.0 | Not found in scan | 0.40.0 |
| CVE-2026-25681 | High | golang.org/x/net | v0.38.0 | Not found in scan | 0.55.0 |
| CVE-2026-27136 | High | golang.org/x/net | v0.38.0 | Not found in scan | 0.55.0 |
| CVE-2026-33814 | High | golang.org/x/net | v0.38.0 | Not found in scan | 0.53.0 |
| CVE-2026-39821 | High | golang.org/x/net | v0.38.0 | Not found in scan | 0.55.0 |
| CVE-2026-46600 | High | golang.org/x/net | v0.38.0 | Not found in scan | 0.56.0 |
| CVE-2026-78659 | High | golang.org/x/net | v0.38.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78660 | High | golang.org/x/net | v0.38.0 | v0.58.0 | 0.60.0 |
| CVE-2026-78669 | High | golang.org/x/net | v0.38.0 | v0.58.0 | 0.60.0 |
| CVE-2026-97032 | High | golang.org/x/net | v0.38.0 | v0.58.0 | 0.60.0 |
| CVE-2026-56851 | High | golang.org/x/text | v0.23.0 | Not found in scan | 0.41.0 |
| CVE-2026-56852 | High | golang.org/x/text | v0.23.0 | Not found in scan | 0.39.0 |
| CVE-2026-84304 | High | google.golang.org/grpc | v1.71.1 | Not found in scan | 1.83.1 |
| CVE-2026-84445 | High | google.golang.org/grpc | v1.71.1 | Not found in scan | 1.82.2, 1.83.2, 1.84.0-dev.0.20260825144003-d5a41119e0e3, 1.85.0-dev.0.20260825072537-93e31b48545e |
| GHSA-hrxh-6v49-42gf | High | google.golang.org/grpc | v1.71.1 | Not found in scan | 1.82.1 |
| CVE-2026-50151 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.1 |
| CVE-2026-50163 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.2 |
| CVE-2026-85731 | High | oras.land/oras-go/v2 | v2.5.0 | Not found in scan | 2.6.2 |
| CVE-2025-58187 | High | stdlib | go1.23.12 | Not found in scan | 1.24.9, 1.25.3 |
| CVE-2025-58188 | High | stdlib | go1.23.12 | Not found in scan | 1.24.8, 1.25.2 |
| CVE-2025-61723 | High | stdlib | go1.23.12 | Not found in scan | 1.24.8, 1.25.2 |
| CVE-2025-61725 | High | stdlib | go1.23.12 | Not found in scan | 1.24.8, 1.25.2 |
| CVE-2025-61726 | High | stdlib | v1.23.12 | Not found in scan | 1.24.12, 1.25.6 |
| CVE-2025-61729 | High | stdlib | v1.23.12 | Not found in scan | 1.24.11, 1.25.5 |
| CVE-2026-111943 | High | stdlib | v1.23.12 | v1.25.13 | 1.26.10, 1.27.3 |
| CVE-2026-25679 | High | stdlib | v1.23.12 | Not found in scan | 1.25.8, 1.26.1 |
| CVE-2026-27145 | High | stdlib | v1.23.12 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-32280 | High | stdlib | v1.23.12 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-32281 | High | stdlib | v1.23.12 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-32283 | High | stdlib | v1.23.12 | Not found in scan | 1.25.9, 1.26.2 |
| CVE-2026-33811 | High | stdlib | v1.23.12 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33814 | High | stdlib | v1.23.12 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-33818 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39820 | High | stdlib | v1.23.12 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-39821 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-39822 | High | stdlib | v1.23.12 | Not found in scan | 1.25.12, 1.26.5, 1.27.0-rc.2 |
| CVE-2026-39836 | High | stdlib | v1.23.12 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42499 | High | stdlib | v1.23.12 | Not found in scan | 1.25.10, 1.26.3 |
| CVE-2026-42504 | High | stdlib | v1.23.12 | Not found in scan | 1.25.11, 1.26.4 |
| CVE-2026-56853 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56858 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56859 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56860 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56862 | High | stdlib | v1.23.12 | Not found in scan | 1.25.13, 1.26.6, 1.27.0-rc.3 |
| CVE-2026-56866 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-78659 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9 |
| CVE-2026-78660 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9 |
| CVE-2026-78667 | High | stdlib | v1.23.12 | v1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-78669 | High | stdlib | v1.23.12 | v1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-94439 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-94440 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-97031 | High | stdlib | v1.23.12 | v1.25.13 | 1.26.9, 1.27.2 |
| CVE-2026-97032 | High | stdlib | go1.23.12 | go1.25.13 | 1.26.9 |
How this is measured
For each release, the latest open source images from ghcr.io/kyverno and the latest Nirmata Enterprise for Kyverno images from ghcr.io/nirmata are scanned in the same run: kyverno, kyvernopre, background-controller, cleanup-controller, reports-controller, kyverno-cli.
- Scanners: Trivy 0.74.0 (database updated October 28, 2026) and Grype 0.117.0 (database built October 28, 2026).
- Severity: critical and high only. No suppressions or VEX statements applied.
- Platform:
linux/amd64. Findings deduplicated by CVE ID and package within each release. - Scan date: October 28, 2026.
- Kyverno's own code is matched by version number. N4K versions carry an
-n4ksuffix, which scanners read as older than the matching open source release, so scan results are not reliable for Kyverno-code findings on N4K images. The status of those advisories is verified against the code on each release branch instead, and is shown above.
The CVEs fixed in each build are listed in the Nirmata Enterprise for Kyverno release notes. For the advisories themselves, see Kyverno CVEs and security advisories.
Frequently asked questions
Does Kyverno open source backport security fixes to older releases?
Per the Kyverno security policy, fixes land in the main branch and may be backported to one prior minor release, depending on severity and feasibility. Older releases keep their CVEs until you upgrade.
Which Kyverno releases does Nirmata Enterprise for Kyverno patch?
The current release and the four before it: Kyverno 1.14 to 1.19 in this scan. Nirmata rebuilds every image on a patched Go toolchain and dependencies, and backports fixes for Kyverno's own code. The release notes list the fixes in each build.
Do hardened container images fix CVEs in Kyverno itself?
No. Hardened and minimal images rebuild Kyverno on a clean base and newer dependencies, which removes OS and library CVEs. A vulnerability in Kyverno's own code stays until the code is fixed, and on an older release that takes a backport. Nirmata Enterprise for Kyverno backports those fixes, and is also available on a hardened base through Chainguard Commercial Builds.
Why do some Nirmata Enterprise for Kyverno images still show CVEs?
Images are scanned against the vulnerability databases as they are on the scan date. A CVE published after an image was built shows up until the next build ships the fix. The table below lists each finding, the version installed, and the version that fixes it.
How are the CVEs counted?
Each image is scanned with Trivy and Grype. Findings rated critical or high are kept, deduplicated by CVE ID and package, and counted once per release across the 6 published images. The CVEs fixed in each Nirmata Enterprise for Kyverno build are listed in the release notes.
Stop choosing between an emergency upgrade and an unpatched Kyverno
Get patched builds for the version you run today, from the team that created Kyverno.