CRI-O has Potential High Memory Consumption from File Read
Published 20 Aug 2025 · Updated 29 Aug 2025
Is your project on an affected github.com/cri-o/cri-o?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <=1.33.3
- Fixed in
- No fix released
Details
There's a vulnerability in the CRI-O application where when container is launched with securityContext.runAsUser specifying a non-existent user, CRI-O attempts to create the user, reading the container's entire /etc/passwd file into memory. If this file is excessively large, it can cause the a high memory consumption leading applications to be killed due to out-of-memory. As a result a denial-of-service can be achieved, possibly disrupting other pods and services running in the same host.
Is GHSA-8f93-j3fx-72f3 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/cri-o/cri-o, and gives you the command that fixes it.
More advisories for github.com/cri-o/cri-o
- LowCVE-2025-0750CRI-O Path Traversal vulnerability in github.com/cri-o/cri-o · 29 Jan 2025
- MediumCVE-2025-0750CRI-O Path Traversal vulnerability · 28 Jan 2025
- LowCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access in github.com/cri-o/cri-o · 4 Dec 2024
- MediumCVE-2024-8676CRI-O: Maliciously structured checkpoint file can gain arbitrary node access · 26 Nov 2024
- LowCVE-2022-4318CRI-O vulnerable to /etc/passwd tampering resulting in Privilege Escalation in github.com/cri-o/cri-o · 21 Aug 2024
- LowCVE-2022-2995CRI-O incorrect handling of supplementary groups may lead to sensitive information disclosure in github.com/cri-o/cri-o · 21 Aug 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.