CVE-2026-62146: Cri-o: sandbox state poisoning via pod annotations may expose runtime socket
Red Hat · Red Hat OpenShift Container Platform 4.16
Vendor fix available · Affected: Red Hat OpenShift Container Platform 4.16 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 6% of scored CVEs
DescriptionCVE.org
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.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Red Hat · Red Hat OpenShift Container Platform 4.16Versions not stated
- Red Hat · Red Hat OpenShift Container Platform 5Versions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Red Hat
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-62146 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.