VulnerabilityPublished 14 Aug 2026Updated 20 Aug 2026

CVE-2026-74240: Red Hat OpenShift Update Service · Improper Authentication

Affects Red Hat OpenShift Update ServiceSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium · patch available : update Red Hat OpenShift Update Service when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat OpenShift Update Service	Affected–	Fixed in–
Red HatRed Hat Quay 3	Affected–	Fixed in–

AI-suggested

Red Hat Quay administrators should configure federated robot authentication with specific audiences to enable enforcement of audience verification ('verify_aud'). Additionally, existing federation configurations should be reviewed and updated to explicitly include and enforce the 'azp' and 'sub' claims to prevent bypasses when these claims are missing. After applying these configuration changes, affected Quay services may require a restart. Since this is a cloud service, Red Hat manages remediation for the hosted service; administrators should follow the vendor advisory for detailed configuration steps and updates.

Description

A flaw was found in Red Hat Quay's JWT (JSON Web Token) validation for federated robot accounts and single sign-on (SSO) authentication. Multiple issues related to audience verification and the enforcement of `azp` and `sub` claims were identified. These flaws could allow an attacker with a validly-signed token from the same identity provider to bypass configured security restrictions. This bypass could lead to unauthorized access by circumventing intended audience, subject, or authorized-client limitations.

Impact

The vulnerability allows an attacker with a valid token from the same identity provider to bypass audience, subject, or authorized-client restrictions, potentially granting unauthorized access to resources or functionality. The impact is limited to confidentiality and integrity with no availability impact. Exploitation requires possession of a valid token, which limits the attack surface. There are no known exploits in the wild at this time.

Summary

This vulnerability in Red Hat Quay's JWT validation affects federated robot accounts and SSO authentication by failing to properly enforce audience verification and checks on the 'azp' and 'sub' claims. An attacker possessing a validly-signed token from the same identity provider can bypass security restrictions configured to limit access based on these claims. The issue arises from default configurations that do not enforce audience verification and insufficient claim checks in certain scenarios. The vulnerability is rated medium severity with a CVSS 3.1 score of 5.4. Exploitation requires a valid token from the same IdP, which restricts the attack vector. Red Hat's advisory recommends configuring federated robot authentication with specific audiences to enable 'verify_aud' enforcement and updating federation configurations to explicitly enforce 'azp' and 'sub' claims. A service restart may be necessary after applying these configuration changes.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Aug 2026, 12:23 UTC

Technical details

References

Community reviews

Related threats