Skip to content
Fencer Intel
high 7.8

CVE-2026-62146 json

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

published 2mo ago modified 12d ago also EUVD-2026-89789 , GHSA-6wmc-5877-hgc9

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository cri-o/cri-o. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits
0
none known

Summary

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.

Patch / fix

  • Red Hat Red Hat OpenShift Container Platform 4.16 0:1.29.13-16.rhaos4.16.git84cfdc6.el8

Is CVE-2026-62146 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-62146 updated cvss 7.8

cri-o: cri-o: Sandbox state poisoning via pod annotations may expose runtime socket

  • Red Hat OpenShift Container Platform 5 cri-o
    affected: workaround, no fix available
  • Red Hat OpenShift Container Platform 4.16 cri-o 1.29.13-16.rhaos4.16.git84cfdc6.el8, cri-o 1.29.13-16.rhaos4.16.git84cfdc6.el9
    fixed: vendor fix RHSA-2026:89713
  • Red Hat OpenShift Container Platform 4.16 cri-tools 1.29.0-10.el8, cri-tools 1.29.0-10.el9, rv 5.14.0-427.158.1.el9_4, runc 1.2.9-6.rhaos4.16.el8, runc 1.2.9-6.rhaos4.16.el9, perf 5.14.0-427.158.1.el9_4, +105 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last mo.

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected products

  • Red Hat Red Hat OpenShift Container Platform 4.16
  • Red Hat Red Hat OpenShift Container Platform 5

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of cri-o/cri-o published their own advisory on GitHub. Reviewed sources take precedence over it.