Skip to main content
VulnerabilityPublished Updated

CVE-2026-15801: Red Hat OpenShift Container Platform 4 · Improper Limitation of a Pathname to a Restricted Directory

Affects Red Hat OpenShift Container Platform 4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.0 High.

Data as of 5 Nov 2026, 11:40 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.18.0
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat OpenShift Container Platform 4cri-oAffected–Fixed in–
Red Hat OpenShift Container Platform 5cri-oAffected–Fixed in–

AI-suggested

Red Hat recommends the following mitigations until security updates are available: (1) Do not enable container checkpoint and restore functionality unless explicitly required. (2) Restrict permissions to create workloads and access node-level container runtime interfaces to trusted administrators only. (3) Avoid restoring containers from untrusted or unverified checkpoint sources. Users should monitor Red Hat advisories for forthcoming patches and apply them once released.

Description

A vulnerability was found in CRI-O related to the container checkpoint and restore feature. When CRI-O is configured to restore containers from checkpoint archives, insufficient validation of restore metadata may allow a user with sufficient privileges to perform unintended operations on the host filesystem. Successful exploitation requires that container checkpoint and restore functionality is enabled, which is not the default configuration. An attacker must also be able to trigger restoration of a container from untrusted checkpoint content.

References

Community reviews

Loading reviews…