CVE-2025-4437: CRI-O has Potential High Memory Consumption from File Read
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.
Published Aug 20, 2025 · Updated Aug 29, 2025
Affected packages
github.com/cri-o/cri-o
- Ecosystem
- Go
- Affected
- <= 1.33.3
- Fixed in
- No patched version yet
- Check
go list -m github.com/cri-o/cri-o
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2025-0750
CRI-O Path Traversal vulnerability
medium6.6No fixJan 28, 2025CVE-2024-8676
CRI-O: Maliciously structured checkpoint file can gain arbitrary node access
medium7.4Nov 26, 2024CVE-2024-5154
malicious container creates symlink "mtab" on the host External
high8.1Jun 4, 2024CVE-2024-3154
CRI-O vulnerable to an arbitrary systemd property injection
high7.2Apr 30, 2024CVE-2023-6476
CRI-O's pods can break out of resource confinement on cgroupv2
medium6.5Jan 10, 2024
