CVE-2026-115424
Description
A flaw was found in the OpenShift client oc. When extracting container image layers with oc image extract, the application fails to properly sanitize symbolic and hard link targets pointing to absolute paths or to sibling directories of the extraction destination. An attacker who supplies a malicious container image can exploit this vulnerability by embedding links, and a chained file entry, that reference locations outside the intended extraction directory. This allows the attacker to write attacker-controlled content to arbitrary locations on the host filesystem with the privileges of the user running the command, potentially leading to file modification outside the destination directory.
Statement
A flaw was found in the oc command-line client used with Red Hat OpenShift. When oc image extract unpacks a container image's layers, symlink and hardlink entries are validated using a computed path, but the symlink is still created using the raw target from the archive, and the target containment check uses a string-prefix comparison rather than a path-boundary comparison. As a result, a link whose target is an absolute path, or a relative path matching the destination directory's name as a text prefix, can pass the check while the link on disk points outside the intended extraction directory. A subsequent archive entry that traverses the planted link is written through it, because the per-entry name check does not inspect intermediate path components for symlinks.
An attacker who can supply or influence a container image that a user extracts with oc image extract (for example an untrusted or compromised image in a registry) may cause files to be written outside the extraction directory, with attacker-controlled content, at locations where a directory already exists. This is most relevant to scripted or CI use of oc image extract where the destination path is fixed and predictable.
The specific affected versions and update streams are being determined as part of this flaw's assessment. Red Hat is evaluating fixes for affected products. Customers should only run oc image extract against trusted container images until an updated oc client is available in their environment.
Mitigation
Treat container images as trusted inputs when using oc image extract. Do not extract images from registries or publishers you do not control or have not verified.
Where possible, run oc image extract as an unprivileged user and into a dedicated, isolated destination directory, and avoid fixed/predictable destination paths in automated or CI pipelines. Restrict who can modify the image references that automated extraction jobs consume.
There is no configuration option to disable only this link-extraction behavior. Apply updated oc client packages or rebuilt platform images when Red Hat publishes them for your product and stream.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.5 | N/A | 5.5 |
| Attack Vector | Local | N/A | Local |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
cve.org: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Acknowledgements
Red Hat would like to thank Yashashree Gund for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
