A flaw was found in the Level of Authentication enforcement mechanism of Keycloak, an identity and access management solution. The issue occurs when a client specifically requires a higher security level for a user who already has an active session at a lower level. Due to a logic error in how session re-evaluations are handled, Keycloak may incorrectly issue a token at the lower security level instead of enforcing the required higher level, potentially allowing unauthorized access to sensitive resources that rely on these security claims.
CVE-2026-97176
Score 4.2 from GitHub Security Advisory published 2026-09-24. a secondary CVSS source baseline 4.2; 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
- 4.2
- EG Score
- 4.2(high)
- EG Risk
- 23(Track)EG Risk 23/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 computedSeverity42% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (2)
Auto-updated Sep 24, 20262539964 – (CVE-2026-97176) CVE-2026-97176 keycloak-services: keycloak-services: Essential acr requirement silently bypassed via Cookie authenticator
https://bugzilla.redhat.com/show_bug.cgi?id=2539964CVE-2026-97176 - 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-97176Vendor Advisories for CVE-2026-97176(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 6× in last 7d / 6× 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-09-24 15:07 UTCEG score recompute
- 2026-09-24 15:07 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 06:23 UTCEG score recompute
- 2026-09-24 05:55 UTCEG score recompute
- 2026-09-24 05:55 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-97176?
When was CVE-2026-97176 disclosed?
Is CVE-2026-97176 actively exploited?
What is the CVSS score of CVE-2026-97176?
How do I remediate CVE-2026-97176?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97176
Is Your Infrastructure Affected by CVE-2026-97176?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.