Advisory

GHSA-8f93-j3fx-72f3

Also known as: CVE-2025-4437, GO-2025-3897

Summary

CRI-O has Potential High Memory Consumption from File Read

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2025-08-20 15:31 UTC
Modified
2025-08-29 20:38 UTC

Affected packages and fixes

github.com/cri-o/cri-o

Go · All systems

Affected

  • introduced 0, last affected 1.33.3 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences