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.
CVE-2026-74240
Score 5.4 from GitHub Security Advisory published 2026-08-15. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 29(Track)EG Risk 29/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
August 14, 2026
Last Modified
August 18, 2026
Advisory Details (2)
Auto-updated Aug 14, 20262516139 – (CVE-2026-74240) CVE-2026-74240 quay: JWT claim validation bypasses in Quay federated robot and SSO authentication
https://bugzilla.redhat.com/show_bug.cgi?id=2516139CVE-2026-74240 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-74240Vendor Advisories for CVE-2026-74240(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:41 UTCGHSA enrichment
- 2026-08-18 15:18 UTCEG score recompute
- 2026-08-18 15:18 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 03:10 UTCEG score recompute
- 2026-08-18 03:10 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:52 UTCEG score recompute
- 2026-08-17 01:52 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-16 00:36 UTCEG score recompute
- 2026-08-16 00:36 UTCGHSA enrichment
- 2026-08-14 23:19 UTCEG score recompute
- 2026-08-14 22:49 UTCEG score recompute
- 2026-08-14 22:48 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-74240?
When was CVE-2026-74240 disclosed?
Is CVE-2026-74240 actively exploited?
What is the CVSS score of CVE-2026-74240?
How do I remediate CVE-2026-74240?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-74240
Is Your Infrastructure Affected by CVE-2026-74240?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.