CVE-2026-74243: Red Hat OpenShift Update Service · Missing Authentication for Critical Functionality
Affects Red Hat OpenShift Update ServiceSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 12 Nov 2026, 23:24 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 6.5 |
|---|
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 14 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat OpenShift Update Serviceopenshift-update-service/openshift-update-service-rhel8 | Affected– | Fixed in– |
| Red Hat Quay 3quay/quay-rhel8 | Affected– | Fixed in– |
| Red Hat Quay 3quay/quay-rhel9 | Affected– | Fixed in– |
AI-suggested
To mitigate this vulnerability, configure the SECURITY_SCANNER_V4_PSK pre-shared key in standalone Red Hat Quay installations. This enables authentication on the security scanner notification endpoint and prevents unauthenticated access. A restart of the Quay service may be required for the changes to take effect. Operator-managed deployments are not affected as they generate this key automatically.
Description
CVE-2026-74243 is a vulnerability in Red Hat Quay where, if the SECURITY_SCANNER_V4_PSK (pre-shared key) is not configured, unauthenticated remote attackers can send POST requests to the security scanner notification endpoint. This can lead to flooding the notification queue and injecting path traversal characters into Clair API URL paths, causing worker resource exhaustion and potential denial of service. The issue primarily affects standalone Quay installations without the pre-shared key set, as operator-managed deployments generate this key automatically.