CVE | Origin Package | Affected Images | severity | Exploitability | status | Detected | Last Update |
|---|---|---|---|---|---|---|---|
| CVE-2025-58187 | pulumi | - | high | - | Fixed | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2025-61732 | pulumi | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-32280 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-27144 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2025-61725 | pulumi | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-32281 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-25679 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-27140 | pulumi | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2025-61729 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2025-61726 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2025-58188 | pulumi | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2025-61723 | pulumi | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2025-61731 | pulumi | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-41567 | promxy-fips | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-34040 | promxy-fips | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-41567 | promxy | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-42306 | promxy-fips | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-34040 | promxy | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-33814 | kuberay-operator-fips | high | - | Fixed | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-29181 | kuberay-operator-fips | high | - | Fixed | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-42306 | promxy | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-24051 | gce-pd-csi-driver-fips-1.26 | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-29181 | gce-pd-csi-driver-fips-1.26 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-29181 | gitlab-runner-fips-18.11 | +1 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-29181 | gce-pd-csi-driver-1.26 | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-39883 | gce-pd-csi-driver-fips-1.26 | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-24051 | gce-pd-csi-driver-1.26 | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-39883 | gce-pd-csi-driver-1.26 | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-33814 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-42504 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-42499 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-42501 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-33811 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-39836 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| CVE-2026-39820 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
| GHSA-p6gq-j5cr-w38f | logto | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-32283 | logto | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-55603 | logto | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2025-58187 | logto | high | - | Pending upstream fix | Jun 22, 2026 | Jul 02, 2026 | |
| CVE-2026-27144 | logto | - | high | - | Unaffected | Jun 22, 2026 | Jul 02, 2026 |
This page is currently not available for mobile devices. For the best experience, please visit us from your computer.