Skip to main content

Red Hat Quay CVE-2026-74240

| EUVDEUVD-2026-58817 MEDIUM
Improper Authentication (CWE-287)
2026-08-14 redhat GHSA-3vf7-35c7-wgcv
5.4
CVSS 3.1 · NVD
Share

Severity by source

Vendor (redhat) PRIMARY
MEDIUM
qualitative
NVD
5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
vuln.today AI
5.4 MEDIUM

Network-accessible API (AV:N), low complexity, but requires a valid IdP-issued token (PR:L); partial C and I from unauthorized registry access; no availability impact described.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
Red Hat
5.4 MEDIUM
qualitative

Primary rating from Vendor (redhat).

CVSS VectorNVD

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

Lifecycle Timeline

1
Analysis Generated
Aug 14, 2026 - 23:16 vuln.today

DescriptionNVD

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.

AnalysisAI

JWT claim validation failures in Red Hat Quay's federated robot account and SSO authentication pathways allow an attacker who already holds a legitimately-issued token from the same configured identity provider to bypass audience (aud), authorized party (azp), and subject (sub) restrictions. Affected deployments include Red Hat Quay 3 and Red Hat OpenShift Update Service across all currently tracked versions. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Obtain valid JWT from shared IdP
Delivery
Craft token with target aud/azp/sub claims
Exploit
Submit token to Quay API
Execution
Bypass claim validation checks
Impact
Access unauthorized registry namespaces or robot account resources

Vulnerability AssessmentAI

Exploitation Exploitation requires that the attacker already possess a validly-signed JWT issued by the same identity provider that is configured in the target Red Hat Quay instance - tokens from unrelated or untrusted IdPs are not usable. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 5.4 Medium rating reflects the genuine but bounded nature of the risk: the attack vector is network-accessible (AV:N), complexity is low (AC:L), but low-privilege access is required (PR:L), meaning an attacker must already hold a valid token issued by the same IdP. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who has obtained a valid JWT from the same identity provider integrated with the target Quay instance - whether through credential theft, insider access, or control of a lower-privileged account - submits a token to the Quay API with `aud`, `azp`, or `sub` values targeting a higher-privileged robot account or another user's SSO session. Because Quay fails to enforce these claims strictly, the token is accepted and the attacker gains read or write access to container image repositories they are not authorized to access. …
Remediation Monitor the Red Hat security advisory at https://access.redhat.com/security/cve/CVE-2026-74240 and the associated Bugzilla ticket at https://bugzilla.redhat.com/show_bug.cgi?id=2516139 for patch availability; no exact patched version number was confirmed in the data available at time of analysis, so patch status is described as patch available per vendor advisory pending version confirmation. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Vendor StatusVendor

Share

CVE-2026-74240 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy