Quick answers
- Is CVE-2026-75939 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75939 being exploited in the wild.
- How severe is CVE-2026-75939?
- High severity, with a CVSS score of 7.4, published 21 September 2026.
- Which products and versions are affected?
- Red Hat oc-mirror.
- Is there a fix for CVE-2026-75939?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75939 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-75939?
- Check whether you run Red Hat Oc-Mirror. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability stems from improper verification of PGP cryptographic signatures (CWE-347): the tool checks for signature errors before the entire signed message body is processed, allowing an attacker to craft a PGP message with a valid Red Hat release key ID but a forged signature that bypasses validation. An unauthenticated remote attacker with the ability to intercept or manipulate traffic to the signature endpoint can exploit this to inject malicious container images. A mitigation or patch is not currently available.
Affected products
- Red Hat oc-mirror
Timeline
- 2026-09-21: disclosed