CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2025-14813 | jenkins-2.541 | - | critical | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-47838 | jenkins-2.541 | - | high | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-41178 | cluster-autoscaler-1.33 | - | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39882 | cluster-autoscaler-1.33 | - | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | spire-agent-1.14 | - | high | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | spire-agent-1.14 | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-39882 | spire-agent-1.14 | - | medium | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-46602 | seaweedfs-cosi-driver-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | seaweedfs-cosi-driver-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | seaweedfs-cosi-driver-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-49835 | spire-agent-1.14 | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-46602 | ollama-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | ollama-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | ollama-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46602 | kubescape | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | kubescape | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-33813 | kubescape | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | kubescape | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | kubescape | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-49349 | kube-arangodb-fips | - | unknown | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | hugo-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | hugo | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46602 | hugo-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | hugo-fips | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46602 | hugo | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | hugo | - | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-49835 | crossplane-2.2-fips | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-49835 | crossplane-2.3-fips | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | crossplane-2.2-fips | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-49835 | crossplane-2.2 | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | crossplane-2.3-fips | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | crossplane-2.2 | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | connaisseur | - | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | connaisseur | - | high | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-49835 | connaisseur | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-49478 | connaisseur | - | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39882 | connaisseur | - | medium | - | Fixed | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | cluster-api-ipam-provider-in-cluster-fips | - | high | - | Fixed | Jun 25, 2026 | Jul 02, 2026 |
| CVE-2026-24051 | cluster-api-ipam-provider-in-cluster-fips | - | high | - | Fixed | Jun 25, 2026 | Jul 02, 2026 |
| CVE-2026-41178 | cluster-api-ipam-provider-in-cluster-fips | - | medium | - | Under review | Jul 02, 2026 | Jul 02, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.