CVE-2026-62146Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket
Updated under an hour ago ()
Does this affect you?
It affects Red Hat OpenShift Container Platform 4. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.11%, higher than 1% of scored CVEs.
Do this next
Free account, 1 product
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
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
- Weakness (CWE)
- CWE-501
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.11% (percentile 1)
- Assigned by
- redhat
- NVD analysis
- Awaiting Analysis
- Record last updated
- Sep 30, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Red Hat Red Hat OpenShift Container Platform 4 redhat:openshift | 4 | CNA record |
References
- https://access.redhat.com/security/cve/CVE-2026-62146vdb-entry, x-refsource-redhat
- https://bugzilla.redhat.com/show_bug.cgi?id=2499618issue-tracking, x-refsource-redhat
- https://github.com/cri-o/cri-o/security/advisories/GHSA-6wmc-5877-hgc9
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.