oc-mirror EUVD-2026-89959

Exploitation requires that an operator run oc-mirror to mirror an operator catalog using specifically the legacy v1 path (--v1) OR the OCI feature path (--use-oci-feature); catalogs mirrored via other/default modern paths are not indicated as affected. The attacker must control or tamper with the operator catalog image being mirrored so its layers contain tar entries with directory-traversal paths. Limiting factors: the vector is local (AV:L) and requires user interaction (UI:R) - an administrator must actively initiate the mirror against the malicious catalog; impact scope is bounded by the filesystem privileges of the user running oc-mirror.

This is a moderate, defender-actionable issue rather than an urgent internet-facing emergency. The CVSS 3.1 vector (7.3) is explicitly LOCAL (AV:L) and requires user interaction (UI:R), meaning exploitation depends on an operator running oc-mirror against a malicious or tampered operator catalog image - not on a remote unauthenticated network request. PR:N reflects that no prior authentication to the tool is needed, but the practical gate is that a privileged operator must voluntarily initiate a mirror of an attacker-influenced catalog. No EPSS score, KEV listing, or public POC was provided in the input, so exploitation status is: no public exploit identified at time of analysis. SSVC framework data was not supplied. The C:H/I:H rating in the vendor vector is generous for what is fundamentally a tar-extraction path-traversal arbitrary-file-write (classic 'tar slip'); the confirmed primary impact is integrity (arbitrary file write), with confidentiality being indirect at best. Bottom line: real but conditional - a supply-chain/registry-poisoning style flaw that matters most to organizations doing disconnected/air-gapped OpenShift mirroring, not a mass-exploitable network vulnerability.

An attacker publishes or tampers with an operator catalog image so that its layers contain tar entries with paths like ../../../../etc/cron.d/x or overwriting binaries in the operator's home. When an OpenShift administrator runs oc-mirror with the legacy --v1 path or the --use-oci-feature OCI path to mirror that catalog, the unvalidated tar extraction writes files outside the intended destination directory, potentially overwriting sensitive files or planting executable content with the privileges of the user running the mirror. No public exploit code was identified in the provided data.