Red Hat has disclosed an Important OpenShift vulnerability that could allow attackers to bypass release-image signature verification and insert malicious payloads into disconnected registries.
Tracked as CVE-2026-75939, the issue affects the oc-mirror utility and carries a CVSS v3.1 score of 7.4.
The flaw stems from an error in how openshift/oc-mirror validates PGP-signed OpenShift release images. The utility checks for a signature error before processing the complete signed message body.
Red Hat OpenShift Flaw
That ordering defect can cause the signature-verification process to accept a crafted PGP message even though its signature is forged. An attacker would need to intercept or manipulate traffic between oc-mirror and the endpoint used to retrieve release signatures.
They could then provide a malicious PGP message that references a legitimate Red Hat release key ID, while containing a forged signature and an attacker-controlled release payload. Because the key identifier appears valid, the defective verification flow may incorrectly accept the content as trusted.
The vulnerability is especially significant for air-gapped and disconnected OpenShift deployments.
Organizations commonly use oc-mirror to copy release images, Operator catalogs, and related content into an internal registry before deploying or updating clusters that cannot directly access external registries.
If exploited, CVE-2026-75939 could poison that internal trust path. A malicious release image accepted by oc-mirror may be mirrored into a disconnected registry and subsequently used by administrators or automated deployment workflows.
This creates a supply-chain compromise scenario in which the payload appears to originate from a trusted release-mirroring process.
Red Hat said successful exploitation could compromise the integrity of software deployments. The CVSS vector identifies network access, high attack complexity, no required privileges, and no user interaction: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N.
The rating also reflects potential high confidentiality and integrity impact, while availability impact is listed as none.
Red Hat lists the openshift4/oc-mirror-plugin-rhel9 component in Red Hat OpenShift Container Platform 4 as affected. The openshift4/oc-mirror-plugin-rhel8 component is marked as not affected because the component is not present.
At publication, Red Hat had not listed an associated security erratum for the affected RHEL 9 plugin.
The weakness is classified as CWE-347, “Improper Verification of Cryptographic Signature.” In practical terms, the defect does not break PGP cryptography itself; it undermines the application logic that determines whether a signed object has been fully and successfully verified.
Red Hat stated that no mitigation meeting its standard criteria was available when it published the advisory on September 21, 2026. Organizations using oc-mirror should therefore treat the signature-retrieval path as a high-value security boundary.
Security teams should restrict and monitor outbound connectivity from mirroring hosts, prevent unauthorized traffic interception through trusted network controls, and investigate mirror logs for unexpected release sources, digest changes, or anomalous signature responses.
Administrators should also validate mirrored release-image digests against independently obtained trusted values before promoting content to production registries.
Until a vendor fix or updated errata becomes available, teams should review all disconnected-registry ingestion workflows, as successful exploitation could transform a trusted OpenShift update mechanism into a vehicle for malicious code deployment.
Join 16,000+ SOC teams using ANY.RUN to streamline threat investigations and reduce manual effort. Explore for your team