Skip to content
Threat Feed
high advisory

CRI-O Checkpoint and Restore Metadata Validation Vulnerability

A vulnerability in the CRI-O container checkpoint and restore feature (CVE-2026-15801) allows an authenticated user to perform unauthorized host filesystem operations through insufficient metadata validation.

CVE search metadata

CVE search record: CVE-2026-15801. Severity: high. CVSS: 8.0. KEV: no. Product: CRI-O. Brief: CRI-O Checkpoint and Restore Metadata Validation Vulnerability. Brief link: https://feed.craftedsignal.io/briefs/2026-09-crio-checkpoint-vuln/

CVE-2026-15801 is a security vulnerability identified in the CRI-O container runtime, specifically impacting the optional container checkpoint and restore functionality. The vulnerability arises from improper validation of metadata contained within checkpoint archives during the restoration process. If an administrator has explicitly enabled the non-default checkpoint and restore feature, an attacker with sufficient privileges to interact with the container runtime can supply a maliciously crafted checkpoint archive. This allows the attacker to manipulate the host filesystem beyond the intended scope of the container's isolated environment. Because this feature is not enabled by default, organizations only face risk if they have modified their CRI-O configuration to support container migration or state snapshots. Defenders should audit their container host configurations to identify if this feature is in use.

Impact

Successful exploitation of this vulnerability permits an attacker to escape container isolation constraints, leading to unauthorized read or write access to the host filesystem. This could result in host compromise, persistence establishment, or the modification of sensitive system files. The scope of impact is limited to environments where the non-default checkpoint and restore functionality is active.

Recommendation

  • Audit all CRI-O container runtime configurations to determine if the checkpoint and restore feature is enabled.
  • Disable the checkpoint and restore feature in CRI-O unless it is strictly required for business operations.
  • Apply security patches or updates for CRI-O provided by the vendor or distribution maintainer to address the metadata validation logic flaw in CVE-2026-15801.
  • Implement strict RBAC controls to ensure that only highly trusted users have the authorization to trigger container checkpoint and restore operations.

Immediate actions

Audit CRI-O configuration across all container nodes for the presence of enabled checkpoint/restore features.

Infrastructure Engineering 48h

Mitigations

Disable checkpoint/restore functionality in CRI-O configuration files if not actively required for operations.

immediate Infrastructure Engineering

CVE-2026-15801