Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket
Historical advisory recorded 27 Oct 2026 22:45:55 UTC. Read the latest advisory.
cve-program · CVE-2026-62146
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
cve-program · CVE-2026-62146
PublishedCri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket
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.
- Source published
- 30 Sep 2026 11:49:20 UTC
- Source modified
- 27 Oct 2026 21:55:15 UTC
- Saved here
- 27 Oct 2026 22:45:55 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H