cve.bz

CVE-2026-62146 Trust Boundary Violation

7.8 highEPSS 0.2%Fix available

High (7.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-501 Trust Boundary Violation
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-62146 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-62146?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-62146?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-62146 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat OpenShift Container Platform 4.160:1.29.13-16.rhaos4.16.git84cfdc6.el8

Linux distributions

DistributionReleasePackageFixed inAdvisory
Red Hatopenshift:4.16::el8cri-o, cri-o-debuginfo, cri-o-debugsource0:1.29.13-16.rhaos4.16.git84cfdc6.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8cri-tools, cri-tools-debuginfo, cri-tools-debugsource0:1.29.0-10.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8openshift, openshift-kubelet, openshift-hyperkube and 3 more0:4.16.0-202610221642.p2.g41c4e9b.assembly.stream.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8openshift-clients, openshift-clients-redistributable0:4.16.0-202610221642.p2.gcb89b60.assembly.stream.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8ose-aws-ecr-image-credential-provider0:4.16.0-202610221642.p2.gd39ac87.assembly.stream.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8ose-azure-acr-image-credential-provider0:4.16.0-202610221642.p2.g90fa18b.assembly.stream.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8ose-gcp-gcr-image-credential-provider0:4.16.0-202610221642.p2.g26b43df.assembly.stream.el8RHSA-2026:89713
Red Hatopenshift:4.16::el8skopeo, skopeo-tests2:1.14.5-9.rhaos4.16.el8RHSA-2026:89713
Red Hatopenshift:4.16::el9cri-o, cri-o-debuginfo, cri-o-debugsource0:1.29.13-16.rhaos4.16.git84cfdc6.el9RHSA-2026:89713
Red Hatopenshift:4.16::el9cri-tools, cri-tools-debuginfo, cri-tools-debugsource0:1.29.0-10.el9RHSA-2026:89713
Red Hatopenshift:4.16::el9ignition, ignition-validate, ignition-debuginfo and 2 more0:2.18.0-9.rhaos4.16.el9RHSA-2026:89713
Red Hatopenshift:4.16::el9openshift, openshift-kubelet, openshift-hyperkube and 3 more0:4.16.0-202610221642.p2.g41c4e9b.assembly.stream.el9RHSA-2026:89713
5 more for Red Hat in the JSON and on Red Hat's page.
Azure Linux3cri-ono fix listedAZL-105348

From the distributions' data via OSV.dev: Red Hat Security Data © Red Hat, Inc., CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Red Hat.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This affects CRI-O versions that persist reserved sandbox metadata together with untrusted pod annotations/labels without validating or namespacing them separately and that reload this state as trusted after a restart, including products that bundle CRI-O as their runtime (e.g., OpenShift Container Platform nodes); exploitation requires pod-creation access plus a subsequent CRI-O restart/node reboot and container recreate, so affected-version and exposure-window details will be confirmed once upstream triage completes

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat OpenShift Container Platform 4.16cri-o-0:1.29.13-16.rhaos4.16.git84cfdc6.el8Fixed 2026-10-27RHSA-2026:89713
Red Hat OpenShift Container Platform 5cri-oAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-62146.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • TeamN4C/SG-2026-0026 Harbor Check: matches CVE 0 stars, created
    CVE-2026-62146 CRI-O ShmPath poisoning PoC and exploit

References

Check your stackJSON