A flaw in the OpenShift client oc causes it to miss validation of symbolic and hard link targets when extracting container image layers. An attacker who can supply a malicious image can embed links that point to absolute or sibling paths outside the intended extraction directory. Extracting such an image thus allows the attacker to write attacker‑controlled data to arbitrary locations on the host filesystem with the privileges of the user running oc, potentially modifying system files or installing malware.

Red Hat OpenShift Container Platform 4, including the oc client component. No specific version numbers are listed, but any installation of the current platform that includes the default oc binary is affected.

The CVSS score of 5.5 denotes moderate severity. EPSS is not available, so the current exploitation likelihood is unknown, and the vulnerability is not listed in CISA KEV. The likely attack vector is through an attacker providing a malicious container image to the oc image extract command, which is conceivable in a build pipeline or static image registry scenario. Because the vulnerability operates on the extraction step, an attacker must have the ability to trigger oc extract on the target system, typically by gaining local user access or controlling automated pipelines.