CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HHigh (7.8). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:HExplain 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.
From the CNA's record in the CVE List.
| Product | Fixed in |
|---|---|
| Red Hat OpenShift Container Platform 4.16 | 0:1.29.13-16.rhaos4.16.git84cfdc6.el8 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Red Hat | openshift:4.16::el8 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.29.13-16.rhaos4.16.git84cfdc6.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | cri-tools, cri-tools-debuginfo, cri-tools-debugsource | 0:1.29.0-10.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | openshift, openshift-kubelet, openshift-hyperkube and 3 more | 0:4.16.0-202610221642.p2.g41c4e9b.assembly.stream.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | openshift-clients, openshift-clients-redistributable | 0:4.16.0-202610221642.p2.gcb89b60.assembly.stream.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | ose-aws-ecr-image-credential-provider | 0:4.16.0-202610221642.p2.gd39ac87.assembly.stream.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | ose-azure-acr-image-credential-provider | 0:4.16.0-202610221642.p2.g90fa18b.assembly.stream.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | ose-gcp-gcr-image-credential-provider | 0:4.16.0-202610221642.p2.g26b43df.assembly.stream.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el8 | skopeo, skopeo-tests | 2:1.14.5-9.rhaos4.16.el8 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el9 | cri-o, cri-o-debuginfo, cri-o-debugsource | 0:1.29.13-16.rhaos4.16.git84cfdc6.el9 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el9 | cri-tools, cri-tools-debuginfo, cri-tools-debugsource | 0:1.29.0-10.el9 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el9 | ignition, ignition-validate, ignition-debuginfo and 2 more | 0:2.18.0-9.rhaos4.16.el9 | RHSA-2026:89713 |
| Red Hat | openshift:4.16::el9 | openshift, openshift-kubelet, openshift-hyperkube and 3 more | 0:4.16.0-202610221642.p2.g41c4e9b.assembly.stream.el9 | RHSA-2026:89713 |
| 5 more for Red Hat in the JSON and on Red Hat's page. | ||||
| Azure Linux | 3 | cri-o | no fix listed | AZL-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 rates this Important.
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
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.16 | cri-o-0:1.29.13-16.rhaos4.16.git84cfdc6.el8 | Fixed 2026-10-27 | RHSA-2026:89713 |
| Red Hat OpenShift Container Platform 5 | cri-o | Affected |
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.
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.