CVE-2026-62146

Container escape via poisoned sandbox state

Published Sep 30, 2026 · Updated Sep 30, 2026

Container escape in CRI-O on Red Hat OpenShift Container Platform 4 allows local users to expose the host runtime socket via pod annotations. CRI-O persists attacker-supplied pod annotations over reserved sandbox bookkeeping and later reloads the poisoned state as trusted, causing recreated containers to mount attacker-controlled host paths. Pod creation with arbitrary annotations, a CRI-O restart or node reboot, and container recreation in that sandbox are required; exposure of the CRI-O socket enables container escape.

CVSS severity7.8
High
EPSS probability0.11%
Next 30 days · Oct 18, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Container escape in CRI-O on Red Hat OpenShift Container Platform 4 allows local users to expose the host runtime socket via pod annotations. CRI-O persists attacker-supplied pod annotations over reserved sandbox bookkeeping and later reloads the poisoned state as trusted, causing recreated containers to mount attacker-controlled host paths. Pod creation with arbitrary annotations, a CRI-O restart or node reboot, and container recreation in that sandbox are required; exposure of the CRI-O socket enables container escape.

The record

CVE
CVE-2026-62146
Published
Sep 30, 2026
Updated
Sep 30, 2026
Vendor
389 Directory Server
Product
Red Hat OpenShift Container Platform 4
Classifications
CWE-501, T1611
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 30, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 30, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

389 Directory Server · Red Hat OpenShift Container Platform 4Affected versions are unavailable in this record.

Published CVSS scores

7.8Red HatCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-501Trust Boundary Violation
T1611Escape to Host

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started