PoC Monitor
← All CVEs
CVE-2026-62146published 30 Sep 2026 11:49 UTCData: JSON · API

Red Hat OpenShift Container Platform 4.16

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

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA · CWE-501
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Red Hat Red Hat OpenShift Container Platform 4.16

    Fixed in 0:1.29.13-16.rhaos4.16.git84cfdc6.el8

    Mitigation

    Upgrade Red Hat OpenShift Container Platform 4.16 to 0:1.29.13-16.rhaos4.16.git84cfdc6.el8 or later.

    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.

    References

    Timeline

    Days relative to CVE publication
    -2t=0+2+4+6+8CVE published30 Sep 2026 · t = 0

    No public PoC found yet; not in CISA KEV.

    PoC repositories

    Found on GitHub.

    1 pending

    Pending 1
    RepositoryCreatedStarsAssessment
    TeamN4C/SG-2026-0026 1 Oct 2026 +1 d 0 Pending
    Flags · score 15
    • no network code found (normal for a local exploit)

    Below the suspicion threshold (50); does not change the assessment.

    Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.