Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
There is no complete workaround; until a fix is available, administrators should restrict who can create/update pods and set arbitrary annotations via RBAC/admission policy, minimize unnecessary CRI-O restarts or node reboots and monitor for anomalous container mounts (e.g. under /dev/shm) following runtime restarts, then apply the vendor patch once released.
Wed, 30 Sep 2026 12:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket | |
| First Time appeared |
Redhat
Redhat openshift |
|
| Weaknesses | CWE-501 | |
| CPEs | cpe:/a:redhat:openshift:4 | |
| Vendors & Products |
Redhat
Redhat openshift |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-09-30T11:49:20.363Z
Reserved: 2026-07-13T11:29:50.979Z
Link: CVE-2026-62146
No data.
Status : Received
Published: 2026-09-30T12:17:13.617
Modified: 2026-09-30T12:17:13.617
Link: CVE-2026-62146
No data.
OpenCVE Enrichment
Updated: 2026-09-30T13:30:17Z