Product by Go
Github.com/cri-o/cri-o
12 known vulnerabilities in Github.com/cri-o/cri-o (Go), 0 of them actively exploited (CISA KEV).
Key figures
12
Vulnerabilities
0
Actively exploited (KEV)
0
Used by ransomware
0
Critical
Vulnerabilities
Actively exploited vulnerabilities (CISA KEV) first, then by priority. Click a column header to re-sort the table.
| High | CVE-2022-0811 | CRI-O: Code Injection | 8.8 | |
| High | CVE-2022-1708 | CRI-O: Uncontrolled Resource Consumption | 7.5 | |
| High | CVE-2024-5154 | Cri-o: malicious container can create symlink on host | 8.1 | |
| High | CVE-2024-3154 | Cri-o: arbitrary command injection via pod annotation | 7.2 | |
| High | CVE-2022-4318 | Cri-o: /etc/passwd tampering privesc | 7.8 | |
| High | CVE-2024-8676 | Cri-o: checkpoint restore can be triggered from different namespaces | 7.4 | |
| High | CVE-2023-6476 | Cri-o: pods are able to break out of resource confinement on cgroupv2 | 6.5 | |
| Medium | CVE-2022-0532 | Cri-o: Incorrect Permission Assignment for Critical Resource | 4.2 | |
| High | CVE-2022-2995 | Cri-o: Improper Access Control | 7.1 | |
| Medium | CVE-2025-0750 | Cri-o: cri-o path traversal in log handling functions allows arbitrary unmounting | 6.6 | |
| Medium | CVE-2025-4437 | Cri-o: large /etc/passwd file may lead to denial of service | 5.7 | |
| Medium | CVE-2022-27652 | Cri-o: Incorrect Default Permissions | 5.3 |