A flaw was found in openshift/oc-mirror. The tool incorrectly verifies PGP (Pretty Good Privacy) release image signatures by checking for signature errors before the entire signed body is processed, leading to a bypass of the signature verification. A remote attacker, by intercepting or manipulating network traffic to the signature endpoint, could exploit this to craft a PGP message with a valid Red Hat release key ID but a forged signature. This enables the oc-mirror tool to accept and mirror a malicious release payload into a disconnected registry, potentially compromising the integrity of software deployments.
CVE-2026-75939
Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-21. a secondary CVSS source baseline 7.4; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(high)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 21%
- KEV
- Not listed
Published
September 21, 2026
Last Modified
September 24, 2026
Advisory Details (2)
Auto-updated Sep 21, 20262517976 – (CVE-2026-75939) CVE-2026-75939 openshift/oc-mirror: Release signature verification: OpenPGP SignatureError checked before signed body is consumed
https://bugzilla.redhat.com/show_bug.cgi?id=2517976CVE-2026-75939 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-75939Vendor Advisories for CVE-2026-75939(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 02:35 UTCGHSA enrichment
- 2026-09-24 14:34 UTCEG score recompute
- 2026-09-24 14:34 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 13:39 UTCEG score recompute
- 2026-09-24 13:39 UTCGHSA enrichment
- 2026-09-24 07:52 UTCGHSA enrichment
- 2026-09-23 19:52 UTCEG score recompute
- 2026-09-23 19:52 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-23 07:52 UTCGHSA enrichment
- 2026-09-22 19:52 UTCEG score recompute
- 2026-09-22 19:52 UTCGHSA enrichment
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-22 15:22 UTCGHSA enrichment
- 2026-09-22 03:22 UTCEG score recompute
- 2026-09-22 03:22 UTCGHSA enrichment
- 2026-09-21 15:22 UTCEG score recompute
- 2026-09-21 14:25 UTCEG score recompute
- 2026-09-21 14:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-75939?
When was CVE-2026-75939 disclosed?
Is CVE-2026-75939 actively exploited?
What is the CVSS score of CVE-2026-75939?
How do I remediate CVE-2026-75939?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75939
Is Your Infrastructure Affected by CVE-2026-75939?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.