cri-o
13 vulnérabilités publiées citent ce produit.
Tel que les CNA l’écrivent dans leurs fiches CVE (éditeur et produit) ; les versions sont les leurs.
| CVE | Versions vulnérables | Titre | Sévérité | Publiée | EPSS | Exploitation |
|---|---|---|---|---|---|---|
| CVE-2026-76061 | < 1.34.14 ; 1.35.0 – < 1.35.9 ; 1.36.0 – < 1.36.6 ; … | Cri-o: cri-o: bind_mount_prefix intermediate-symlink prefix bypass | MEDIUM 5.5 | 0.2 % | ||
| CVE-2026-92574 | 1.34.0 – < 1.34.14 ; 1.35.0 – < 1.35.9 ; 1.36.0 – < 1.36.6 | Cri-o: cri-o checkpoint restore bypasses destination security context | HIGH 8.8 | 0.7 % | ||
| CVE-2026-17113 | < 1.34.11 ; < 1.35.7 ; < 1.36.3 | Cri-o: cri-o: unvalidated image env var causes daemon crash | MEDIUM 6.0 | 0.1 % | ||
| CVE-2025-0750 | < 1.33.1 | Cri-o: cri-o path traversal in log handling functions allows arbitrary unmounting | MEDIUM 6.6 | 0.3 % | ||
| CVE-2024-8676 | < 1.29.11 ; 1.30.0 – < 1.30.8 ; 1.31.0 – < 1.31.3 | Cri-o: checkpoint restore can be triggered from different namespaces | HIGH 7.4 | 0.8 % | ||
| CVE-2024-5154 | 1.30.0 – < 1.30.1 ; 1.29.4 – < 1.29.5 ; 1.28.6 – < 1.28.7 | Cri-o: malicious container can create symlink on host | HIGH 8.1 | 1.2 % | ||
| CVE-2024-3154 | 1.27.5 ; 1.28.5 ; 1.29.3 | Cri-o: arbitrary command injection via pod annotation | HIGH 7.2 | 1.4 % | ||
| CVE-2022-2995 | cri-o 1.25.0 | Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data | HIGH 7.1 | 0.4 % | ||
| CVE-2022-1708 | Affects cri-o <= 1.24.0, 1.23.2, 1.22.4, Fixed-in 1.24.1, 1.23.3, 1.22.5 | A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to the Kube API. The ExecS | HIGH 7.5 | 3.2 % | ||
| CVE-2022-27652 | Affects all versions. | A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby ( | MEDIUM 5.3 | 0.2 % | ||
| CVE-2022-0811 | cri-o 1.24.0, cri-o 1.23.2, cri-o 1.22.3, cri-o 1.21.6, cri-o 1.20.7, cri-o 1.19.6 | A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes c | HIGH 8.8 | 19 % | ||
| CVE-2022-0532 | 1.18 | An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for | MEDIUM 4.2 | 0.8 % | ||
| CVE-2019-14891 | n/a | A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. This can result in container man | MEDIUM 5.0 | 0.8 % |