CVE-2026-16102

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive internal claim locations. An attacker with a standard user account and a limited Initial Access Token can exploit this to forge administrative roles in their access token. This allows the attacker to take over other clients, steal confidential secrets, and potentially gain full administrative control over the realm.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/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 computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 5, 2026

Last Modified

August 20, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
Patch available. Sources: redhat.
redhat

2501735 – (CVE-2026-16102) CVE-2026-16102 keycloak-services: keycloak-services: Default DCR policy allows role forgery via User Property mappers

https://bugzilla.redhat.com/show_bug.cgi?id=2501735
redhat Patch Available

CVE-2026-16102 - 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-16102

Vendor Advisories for CVE-2026-16102(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhbk/keycloak-rhel9-operator:26.4-222026-08-05redhat
redhatrhbk-openshift-rhel9/rhbk-openshift-rhel92026-08-05redhat
redhatrhbk/keycloak-rhel9-operator:26.6-112026-08-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 45× in last 7d / 96× 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.

  1. 2026-08-20 11:27 UTCEG score recompute
  2. 2026-08-20 11:27 UTCVendor advisory
  3. 2026-08-20 11:27 UTCGHSA enrichment
  4. 2026-08-20 11:03 UTCEG score recompute
  5. 2026-08-20 11:03 UTCVendor advisory
  6. 2026-08-20 11:03 UTCGHSA enrichment
  7. 2026-08-20 10:29 UTCVendor advisory
  8. 2026-08-20 10:29 UTCGHSA enrichment
  9. 2026-08-19 21:27 UTCEG score recompute
  10. 2026-08-19 21:27 UTCVendor advisory
  11. 2026-08-19 21:27 UTCGHSA enrichment
  12. 2026-08-19 17:03 UTCEPSS rescore
  13. 2026-08-19 08:17 UTCVendor advisory
  14. 2026-08-19 08:17 UTCGHSA enrichment
  15. 2026-08-18 19:16 UTCEG score recompute
  16. 2026-08-18 19:16 UTCVendor advisory
  17. 2026-08-18 19:16 UTCGHSA enrichment
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-18 06:13 UTCVendor advisory
  20. 2026-08-18 06:13 UTCGHSA enrichment
  21. 2026-08-17 17:09 UTCEG score recompute
  22. 2026-08-17 17:09 UTCVendor advisory
  23. 2026-08-17 17:09 UTCGHSA enrichment
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 04:07 UTCVendor advisory
Show 71 more
  1. 2026-08-17 04:07 UTCGHSA enrichment
  2. 2026-08-16 15:05 UTCEG score recompute
  3. 2026-08-16 15:05 UTCVendor advisory
  4. 2026-08-16 15:05 UTCGHSA enrichment
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 02:14 UTCEPSS rescore
  7. 2026-08-16 02:03 UTCVendor advisory
  8. 2026-08-16 02:03 UTCGHSA enrichment
  9. 2026-08-15 13:01 UTCEG score recompute
  10. 2026-08-15 13:01 UTCVendor advisory
  11. 2026-08-15 13:01 UTCGHSA enrichment
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 23:58 UTCVendor advisory
  14. 2026-08-14 23:58 UTCGHSA enrichment
  15. 2026-08-14 10:56 UTCEG score recompute
  16. 2026-08-14 10:56 UTCVendor advisory
  17. 2026-08-14 10:56 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 21:54 UTCVendor advisory
  20. 2026-08-13 21:54 UTCGHSA enrichment
  21. 2026-08-13 08:52 UTCVendor advisory
  22. 2026-08-13 08:52 UTCGHSA enrichment
  23. 2026-08-12 19:50 UTCEG score recompute
  24. 2026-08-12 19:50 UTCVendor advisory
  25. 2026-08-12 19:50 UTCGHSA enrichment
  26. 2026-08-12 13:50 UTCEPSS rescore
  27. 2026-08-12 06:48 UTCVendor advisory
  28. 2026-08-12 06:48 UTCGHSA enrichment
  29. 2026-08-11 17:45 UTCEG score recompute
  30. 2026-08-11 17:45 UTCVendor advisory
  31. 2026-08-11 17:45 UTCGHSA enrichment
  32. 2026-08-11 13:42 UTCEPSS rescore
  33. 2026-08-11 13:08 UTCVendor advisory
  34. 2026-08-11 13:08 UTCGHSA enrichment
  35. 2026-08-11 00:06 UTCEG score recompute
  36. 2026-08-11 00:06 UTCVendor advisory
  37. 2026-08-11 00:06 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 11:04 UTCVendor advisory
  40. 2026-08-10 11:04 UTCGHSA enrichment
  41. 2026-08-09 22:02 UTCEG score recompute
  42. 2026-08-09 22:02 UTCVendor advisory
  43. 2026-08-09 22:02 UTCGHSA enrichment
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-09 09:00 UTCVendor advisory
  46. 2026-08-09 09:00 UTCGHSA enrichment
  47. 2026-08-08 19:58 UTCEG score recompute
  48. 2026-08-08 19:58 UTCVendor advisory
  49. 2026-08-08 19:58 UTCGHSA enrichment
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 06:55 UTCVendor advisory
  52. 2026-08-08 06:55 UTCGHSA enrichment
  53. 2026-08-07 17:53 UTCEG score recompute
  54. 2026-08-07 17:53 UTCVendor advisory
  55. 2026-08-07 17:53 UTCGHSA enrichment
  56. 2026-08-07 04:51 UTCVendor advisory
  57. 2026-08-07 04:51 UTCGHSA enrichment
  58. 2026-08-06 15:49 UTCEG score recompute
  59. 2026-08-06 15:49 UTCVendor advisory
  60. 2026-08-06 15:49 UTCGHSA enrichment
  61. 2026-08-06 13:46 UTCEPSS rescore
  62. 2026-08-06 08:33 UTCVendor advisory
  63. 2026-08-06 08:33 UTCGHSA enrichment
  64. 2026-08-05 19:31 UTCGHSA enrichment
  65. 2026-08-05 17:30 UTCEG score recompute
  66. 2026-08-05 17:30 UTCGHSA enrichment
  67. 2026-08-05 16:29 UTCEG score recompute
  68. 2026-08-05 16:29 UTCGHSA enrichment
  69. 2026-08-05 15:27 UTCEG score recompute
  70. 2026-08-05 14:36 UTCEG score recompute
  71. 2026-08-05 14:35 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-16102?
CVE-2026-16102 is a high vulnerability published on August 5, 2026. A flaw was found in the Dynamic Client Registration (DCR) component of Keycloak, an identity and access management solution. The default DCR policy fails to properly validate the claim path for User Property mappers, allowing them to write values to sensitive internal claim locations. An attacker…
When was CVE-2026-16102 disclosed?
CVE-2026-16102 was first published in the National Vulnerability Database on August 5, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16102 actively exploited?
CVE-2026-16102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.9% of all scored CVEs.
What is the CVSS score of CVE-2026-16102?
CVE-2026-16102 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-16102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16102

Explore →

Is Your Infrastructure Affected by CVE-2026-16102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs