Skip to content
Fencer Vulns
critical 9.1

CVE-2020-1731 json

Predictable password in Keycloak

published 2020-03-02 6 y ago modified 2026-06-17 4 mo ago also GHSA-6pmv-7pr9-cgrj , EUVD-2020-0369

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

A flaw was found in all versions of the Keycloak operator, before version 8.0.2,(community only) where the operator generates a random admin password when installing Keycloak, however the password remains the same when deployed to the same OpenShift namespace.

Patch / fix

  • maven org.keycloak:keycloak-core 8.0.2
  • redhat keycloak_operator 8.0.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-1731 updated cvss 9.1

keycloak: generates same admin password while installation when deployed on same openshift namespace

  • Red Hat Single Sign-On 7 rh-sso7-keycloak rh-sso7-keycloak
    not affected: vulnerable code not present “No known mitigation yet.”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-core
<8.0.2
8.0.2

Affected products

  • Red Hat keycloak

Classification

Weakness
  • CWE-341 Predictable from Observable State
  • CWE-330 Use of Insufficiently Random Values

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.