A flaw was found in Red Hat Quay's JWT (JSON Web Token) validation for federated robot accounts and single sign-on (SSO) authentication. (CVE-2026-74240)
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.
AI Analysis
Technical Summary
CVE-2026-74240 describes a vulnerability in Red Hat Quay's JWT validation mechanism used for federated robot accounts and single sign-on authentication. The flaw arises from default configurations that do not enforce audience verification and insufficient validation of 'azp' (authorized party) and 'sub' (subject) claims in certain scenarios. An attacker with a validly-signed token from the same identity provider can exploit these weaknesses to bypass security restrictions intended to limit access based on audience, subject, or authorized client. The vulnerability is classified under CWE-287 (Improper Authentication) and has a CVSS v3.1 score of 5.4 (medium severity). Exploitation requires possession of a valid token from the same IdP, which restricts the scope of attack. Red Hat has not released a patch but recommends configuration changes to enforce claim verification and audience checks to mitigate the issue.
Potential Impact
The vulnerability allows unauthorized access by bypassing configured security restrictions related to JWT audience, subject, and authorized-client claims. This could lead to exposure of resources or functionality to unintended actors. The impact is limited by the requirement that the attacker must have a valid token from the same identity provider. Confidentiality and integrity impacts are rated low, with no availability impact.
Mitigation Recommendations
Red Hat Quay administrators should configure federated robot authentication with specific audiences to enable enforcement of 'verify_aud'. They must review and update federation configurations to explicitly include and enforce 'azp' and 'sub' claims to prevent bypasses when these claims are missing. A restart of affected Quay services may be necessary after applying configuration changes. No official patch is currently available; patch status is not yet confirmed — check the Red Hat advisory for updates. Follow the detailed configuration guidance in Red Hat Quay documentation.
A flaw was found in Red Hat Quay's JWT (JSON Web Token) validation for federated robot accounts and single sign-on (SSO) authentication. (CVE-2026-74240)
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.
CVSS v3.1
Score 5.4medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-74240 describes a vulnerability in Red Hat Quay's JWT validation mechanism used for federated robot accounts and single sign-on authentication. The flaw arises from default configurations that do not enforce audience verification and insufficient validation of 'azp' (authorized party) and 'sub' (subject) claims in certain scenarios. An attacker with a validly-signed token from the same identity provider can exploit these weaknesses to bypass security restrictions intended to limit access based on audience, subject, or authorized client. The vulnerability is classified under CWE-287 (Improper Authentication) and has a CVSS v3.1 score of 5.4 (medium severity). Exploitation requires possession of a valid token from the same IdP, which restricts the scope of attack. Red Hat has not released a patch but recommends configuration changes to enforce claim verification and audience checks to mitigate the issue.
Potential Impact
The vulnerability allows unauthorized access by bypassing configured security restrictions related to JWT audience, subject, and authorized-client claims. This could lead to exposure of resources or functionality to unintended actors. The impact is limited by the requirement that the attacker must have a valid token from the same identity provider. Confidentiality and integrity impacts are rated low, with no availability impact.
Mitigation Recommendations
Red Hat Quay administrators should configure federated robot authentication with specific audiences to enable enforcement of 'verify_aud'. They must review and update federation configurations to explicitly include and enforce 'azp' and 'sub' claims to prevent bypasses when these claims are missing. A restart of affected Quay services may be necessary after applying configuration changes. No official patch is currently available; patch status is not yet confirmed — check the Red Hat advisory for updates. Follow the detailed configuration guidance in Red Hat Quay documentation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-3vf7-35c7-wgcv
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74240"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
- Is Cloud Service
- true
Threat ID: 6a7ff5e6bf8831d53987df6f
Added to database: 08/15/2026, 05:15:18 UTC
Last enriched: 08/15/2026, 06:14:08 UTC
Last updated: 08/15/2026, 23:41:00 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.