A flaw was found in the JWT Bearer authorization grant implementation within the keycloak-services component of Red Hat Build of Keycloak. This component handles various OAuth2 and OpenID Connect grant types used for issuing access tokens. The issue occurs because the JWT Bearer grant fails to check if a client requires user consent before issuing a token. This allows an authenticated attacker with valid client credentials and a trusted identity provider assertion to bypass the consent requirement and obtain unauthorized access to a user account at a consent-gated client.
CVE-2026-79652
Score 5.9 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 5.9; 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.9
- EG Score
- 5.9(high)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 6%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 25, 20262523347 – (CVE-2026-79652) CVE-2026-79652 keycloak-services: keycloak-services: JWT Bearer authorization grant does not enforce consentRequired
https://bugzilla.redhat.com/show_bug.cgi?id=2523347CVE-2026-79652 - 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-79652Vendor Advisories for CVE-2026-79652(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 18× in last 7d / 18× 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-30 01:22 UTCEPSS rescore
- 2026-08-29 20:40 UTCEG score recompute
- 2026-08-29 20:40 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 21:25 UTCGHSA enrichment
- 2026-08-28 12:03 UTCEG score recompute
- 2026-08-28 12:03 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 12:49 UTCEG score recompute
- 2026-08-27 12:49 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 13:35 UTCGHSA enrichment
- 2026-08-25 14:21 UTCEG score recompute
- 2026-08-25 14:21 UTCGHSA enrichment
- 2026-08-25 13:36 UTCEG score recompute
- 2026-08-25 13:36 UTCGHSA enrichment
- 2026-08-25 11:19 UTCEG score recompute
- 2026-08-25 11:16 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-79652?
When was CVE-2026-79652 disclosed?
Is CVE-2026-79652 actively exploited?
What is the CVSS score of CVE-2026-79652?
How do I remediate CVE-2026-79652?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-79652
Is Your Infrastructure Affected by CVE-2026-79652?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.