CVE-2026-62146: high-severity vulnerability in Red Hat OpenShift Container Platform 4
Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket
Published
41Vexday Risk Score
No sign of exploitation. It has a public proof of concept.
ssvc Attendcvss 7.8epss 0.1%
from disclosure to weapon1 days
Published on NVDSep 30
1st PoC+1d
exploitation probability
0.1%top 99% of all CVEs
observed exploitation
nono source reports it
1 public exploit(s)
A trust-boundary flaw in CRI-O's sandbox state persistence allows attacker-influenced pod metadata to overwrite CRI-O's own reserved sandbox bookkeeping; once reloaded as trusted after a restart, a later container recreate in that sandbox can expose a host-side runtime-management resource inside the container, enabling container escape.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
Red Hat · Red Hat OpenShift Container Platform 4public PoCs found — 1
githubgithub.com/TeamN4C/SG-2026-0026★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — Red Hat OpenShift Container Platform 4
In the same product, most dangerous first.
CVE-2024-6387HIGHOpenssh: regresshion - race condition in ssh allows rce/dosEPSS 99.5%CVE-2024-12084CRITICALRsync: heap buffer overflow in rsync due to improper checksum length handlingEPSS 72.1%CVE-2025-26466MEDIUMOpenssh: denial-of-service in opensshEPSS 40.6%CVE-2025-10230CRITICALSamba: command injection in wins server hook scriptEPSS 39.7%CVE-2026-4480CRITICALSamba: samba: remote code execution in printing subsystem via unescaped job descriptionEPSS 13.9%CVE-2024-12085HIGHRsync: info leak via uninitialized stack contentsEPSS 8.8%