CVE-2026-62146 Cri-o: cri-o: sandbox state poisoning via pod annotations may expose runtime socket

High 7.8 Published Updated

Attackers can poison sandbox state via pod annotations to expose host runtime sockets, enabling container escape and privilege escalation in CRI-O.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-62146?

CVE-2026-62146 is a high-severity vulnerability in Red Hat OpenShift Container Platform 4.16, published on 30 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-501

Which versions are affected by CVE-2026-62146?

How do I fix CVE-2026-62146?

No fix has been published for CVE-2026-62146 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-62146 being exploited?

There is no known exploitation of CVE-2026-62146 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as AZL-105348.

Is CVE-2026-62146 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free