{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-75939 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75939 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75939 is a high-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-75939 and fix it if it is affected.\n\nWhat it is: CVE-2026-75939 is a high-severity vulnerability in Red Hat OpenShift Container Platform 4, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-75939 in the wild and no public exploit code.\n\nAffected product: Red Hat OpenShift Container Platform 4. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-75939/ (Markdown: https://insights.sbomify.com/CVE-2026-75939/index.md)","id":"CVE-2026-75939","markdown":"https://insights.sbomify.com/CVE-2026-75939/index.md","name":"CVE-2026-75939","record":{"aliases":["GHSA-vhqx-cfmx-mjq9"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenShift mirror tool","requires_auth":"none","summary":"Attackers can bypass PGP signature verification in oc-mirror to inject malicious payloads into disconnected registries, compromising deployment integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Openshift/oc-mirror: release signature verification: openpgp signatureerror checked before signed body is consumed","id":"CVE-2026-75939","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Hardcoded credentials in Health Application","id":"CVE-2026-75940"},"packages":[],"prev":{"headline":"OS Command Injection in Digi Accelerated Linux (DAL OS)","id":"CVE-2026-75937"},"products":["Red Hat OpenShift Container Platform 4","Red Hat OpenShift Container Platform 4.18"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Red Hat"]},"summary":"Attackers can bypass PGP signature verification in oc-mirror to inject malicious payloads into disconnected registries, compromising deployment integrity.","url":"https://insights.sbomify.com/CVE-2026-75939/"}