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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Public exploits 1
- TeamN4C/SG-2026-0026 PoC on GitHub
Each line links to the index that lists it, never to exploit code. Exploit-DB's "verified" and a Metasploit rank of good or better count as verified; a PoC-in-GitHub entry is a repository's claim.
Change history 3
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-27 21:55
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-27 22:17
- First seenCVSS 7.8 · red hatNVD modified 2026-10-27 21:55
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.