A flaw was found in the authentication configuration endpoint of the keycloak-services component, which is the core engine for Red Hat Build of Keycloak identity and access management. The issue occurs because the system fails to mask sensitive configuration values, such as reCAPTCHA secret keys, when they are requested by administrators with view-only permissions. This can lead to the exposure of third-party service credentials to unauthorized personnel or through administrative logs.
CVE-2026-16104
Score 4.3 from GitHub Security Advisory published 2026-07-17. a secondary CVSS source baseline 4.3; 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.3
- EG Score
- 4.3(high)
- EG Risk
- 19(Track)EG Risk 19/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 computedSeverity43% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 10.6%
- KEV
- Not listed
Published
July 17, 2026
Last Modified
July 17, 2026
Advisory Details (2)
Auto-updated Jul 17, 20262501737 – (CVE-2026-16104) CVE-2026-16104 keycloak-services: keycloak-services: Authenticator config endpoint exposes raw reCAPTCHA secrets to view-only admins
https://bugzilla.redhat.com/show_bug.cgi?id=2501737Vendor Advisories for CVE-2026-16104(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 9× in last 7d / 13× 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-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-19 02:28 UTCEPSS rescore
- 2026-07-17 18:33 UTCEG score recompute
- 2026-07-17 18:32 UTCGHSA enrichment
- 2026-07-17 16:46 UTCEG score recompute
- 2026-07-17 16:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-522
- CVE-2013-7055EG 9.8EPSS 93%CRITICAL
- CVE-2013-7052EG 9.8EPSS 98%CRITICAL
- CVE-2014-3445EG 9.8EPSS 92%CRITICAL
- CVE-2014-5381EG 9.8EPSS 94%CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2018-1000627EG 9.8CRITICAL
- CVE-2018-11742EG 9.8EPSS 96%CRITICAL
- CVE-2018-1000851EG 9.8CRITICAL
- CVE-2018-10824EG 9.8EPSS 96%CRITICAL
Frequently asked(5)
What is CVE-2026-16104?
When was CVE-2026-16104 disclosed?
Is CVE-2026-16104 actively exploited?
What is the CVSS score of CVE-2026-16104?
How do I remediate CVE-2026-16104?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16104
Is Your Infrastructure Affected by CVE-2026-16104?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.