https://seclists.org/oss-sec/2025/q4/138: runc container bakouts via procfs writes: CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881
Published Nov 5, 2025
·Updated
Affected Software
1 affected component
Open Container Initiative runc
Frequently Asked Questions
1
What is the severity of CVE-2025-31133?
CVE-2025-31133 is classified as a high-severity vulnerability due to its potential impact on runc container security.
2
How do I fix CVE-2025-31133?
To mitigate CVE-2025-31133, you should update to the latest version of runc that addresses this vulnerability.
3
What types of systems are affected by CVE-2025-31133?
CVE-2025-31133 affects systems utilizing the Open Container Initiative runc, particularly those deploying containers on the host OS.
4
What are the risks associated with CVE-2025-31133?
The risks of CVE-2025-31133 include unauthorized access to host resources and potential container breakout, compromising the underlying system.
5
Is there a workaround for CVE-2025-31133 while I update my systems?
While an official workaround may not be available, reducing permissions and isolating affected containers can help minimize risks until updated.