CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2026-53488 | headlamp | - | critical | - | Pending upstream fix | Jun 25, 2026 | Jul 02, 2026 |
| CVE-2025-14813 | jenkins-2.541 | +1 | critical | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-47838 | jenkins-2.541 | +1 | high | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-41178 | cluster-autoscaler-1.33 | +1 | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-39882 | cluster-autoscaler-1.33 | +1 | medium | - | Fix not planned | Jul 01, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | tailscale-fips | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 | |
| CVE-2026-46602 | tailscale-fips | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 | |
| CVE-2026-46604 | tailscale-fips | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 | |
| CVE-2026-39883 | spire-agent-fips-1.14 | high | - | Fixed | Jul 01, 2026 | Jul 02, 2026 | |
| CVE-2026-49835 | spire-agent-fips-1.14 | unknown | - | Fixed | Jul 01, 2026 | Jul 02, 2026 | |
| CVE-2026-39882 | spire-agent-fips-1.14 | medium | - | Fixed | 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-48702 | spire-agent-fips-1.14 | unknown | - | Fixed | Jun 26, 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 | +3 | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-46601 | kubescape | +3 | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-33813 | kubescape | +3 | high | - | Fixed | Jun 27, 2026 | Jul 02, 2026 |
| CVE-2026-48702 | kubescape | +3 | unknown | - | Fixed | Jun 26, 2026 | Jul 02, 2026 |
| CVE-2026-46604 | kubescape | +3 | 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-39984 | crossplane-1.20-fips | medium | - | Fixed | Jun 25, 2026 | Jul 02, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.