How severe is CVE-2026-62146?

CVE-2026-62146 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-62146 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-62146?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-62146 published?

CVE-2026-62146 was published on 2026-09-30.

CVE-2026-62146

CVE-2026-62146 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-501.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-501
Published: 2026-09-30
Last modified: 2026-09-30

Description

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.

Frequently asked questions

What is CVE-2026-62146?: 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.
How severe is CVE-2026-62146?: CVE-2026-62146 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-62146 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-62146?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-62146 published?: CVE-2026-62146 was published on 2026-09-30.

References

Other CWE-501 vulnerabilities

CVE-2026-25725 — Critical (CVSS 10.0): Claude Code is an agentic coding tool. Prior to version 2.1.2, Claude Code's bubblewrap sandboxing mechanism failed to…
CVE-2025-48938 — Critical (CVSS 9.8): go-gh is a collection of Go modules to make authoring GitHub CLI extensions easier. A security vulnerability has been…
CVE-2026-44091 — Critical (CVSS 9.1): An unauthenticated remote attacker can post a malicious ID to the MQTT Broker results in the creation of a new…
CVE-2024-49050 — High (CVSS 8.8): Visual Studio Code Python Extension Remote Code Execution Vulnerability
CVE-2023-28597 — High (CVSS 8.3): Zoom clients prior to 5.13.5 contain an improper trust boundary implementation vulnerability. If a victim saves a local…
CVE-2024-23682 — High (CVSS 8.2): Artemis Java Test Sandbox versions before 1.8.0 are vulnerable to a sandbox escape when an attacker includes class…

Browse all CWE-501 vulnerabilities →