CVE-2026-62146

LOWCVSS 7.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

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

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-501

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Referenced assets1 URL

By indicator

https://github.com/TeamN4C/SG-2026-0026

Full discourse1 post

Ryx@PadhiyarRushi17h
CRI-O sandbox bookkeeping can be overwritten. Restart, then the recreate escapes!! CVE-2026-62146 (CVSS 7.8): Attacker-influenced pod metadata lands in CRI-O's reserved sandbox state. After reload it is trusted. Next container recreate exposes a host runtime resource inside the pod. Updated 30 Sep. Public repro is up!! https://github.com/TeamN4C/SG-2026-0026 #Cybersecurity #AI #AISecurity #MCP #Claude #GPT #Infosec #Trending #CloudSecurity #ContainerEscape #Kubernetes
20032145
952 followersView on X

Explore more

Back to dashboard