VulertSecurity VulertSecurity

Vulnerability Database · Go · github.com/cri-o/cri-o · Version

github.com/cri-o/cri-o v1.35.8

v1.35.8 is affected by 18 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: v1.37.2.

Critical 0 High 1 Medium 7 Low 0 Unrated 10

All github.com/cri-o/cri-o versions & vulnerabilities → Source repository Search the database for this package →
Released 02 Sep 2026 Licence Apache-2.0 Also known from other sources 2 Newer releases 300 Database updated 23/Oct/2026

Release and licence data published by the Go module proxy. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

github.com/cri-o/cri-o v1.35.8 vulnerabilities

18 vulnerabilities cover github.com/cri-o/cri-o v1.35.8. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2024-8676: CRI-O Malicious Checkpoint File Vulnerability Leading to Arbitrary Node Access 7.4 medium 1.29.11 26 Nov 2024
CVE-2022-2995: CRI-O Incorrect Handling of Supplementary Groups 7.1 high 1.25.0 20 Sep 2022
CVE-2025-0750: CRI-O Path Traversal Vulnerability Leading to Node-Level Denial of Service 6.6 medium No fix published 28 Jan 2025
CVE-2022-43183: XXL-JOB vulnerable to Server-Side Request Forgery (SSRF) 6.1 medium 1.26.0 29 Dec 2022
CVE-2022-4318: Privilege Escalation in CRI-O 6.1 medium 1.26.0 29 Dec 2022
CVE-2025-4437: CRI-O High Memory Consumption Vulnerability 5.7 medium No fix published 20 Aug 2025
CVE-2022-27652: Incorrect Default Permissions in CRI-O 4.8 medium 1.24.0 22 Apr 2022
CVE-2022-0532: Incorrect Permission Assignment for Critical Resource in CRI-O 4.2 medium 1.23.1 11 Feb 2022
CVE-2025-4437: High Memory Consumption Vulnerability in CRI-O Package N/A unrated No fix published 29 Aug 2025
CVE-2025-0750: CRI-O Path Traversal Vulnerability in github.com/cri-o/cri-o N/A unrated No fix published 29 Jan 2025
CVE-2024-8676: CRI-O Arbitrary Node Access via Malicious Checkpoint File N/A unrated 1.29.11 04 Dec 2024
CVE-2022-4318: Privilege Escalation in CRI-O N/A unrated 1.26.0 21 Aug 2024
CVE-2022-2989: CRI-O Incorrect Handling of Supplementary Groups N/A unrated 1.25.0 21 Aug 2024
Incorrect Permission Assignment for Critical Resource in CRI-O N/A unrated 1.23.1 21 Aug 2024
CVE-2022-1708: Node DOS by way of memory exhaustion in CRI-O N/A unrated 1.22.5 21 Aug 2024
Incorrect Default Permissions in CRI-O N/A unrated 1.24.0 21 Aug 2024
CVE-2023-6476: Resource Confinement Breakout in CRI-O N/A unrated 1.27.3 28 Jun 2024
CVE-2024-3154: Arbitrary systemd Property Injection in CRI-O N/A unrated 1.27.6 04 Jun 2024

Looking for another version, or everything Vulert holds for github.com/cri-o/cri-o?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/cri-o/cri-o v1.35.8

Is github.com/cri-o/cri-o v1.35.8 vulnerable?

Yes. 18 vulnerabilities in the Vulert database cover github.com/cri-o/cri-o v1.35.8: 0 critical, 1 high, 7 medium and 0 low, plus 10 not yet rated. The upgrade Vulert recommends is v1.37.2, and each entry above names the fixed version to move to.

Which version of github.com/cri-o/cri-o should I use instead of v1.35.8?

v1.37.2 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is v1.35.8 the latest release of github.com/cri-o/cri-o?

No. v1.35.8 was published 02 Sep 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor github.com/cri-o/cri-o for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cri-o/cri-o version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.