Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-3875: A vulnerability was found in keycloak before 6.0.2

38
Routine
MEDIUM 6.5REMOTEWATCHLISTUPGRADEDOWNGRADE

CVE-2019-3875 is a medium-severity flaw (CVSS 6.5) affecting keycloak, single sign-on. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or through the separately configured path. The CRL are often available over the network through unsecured protocols ('http' or 'ldap') and hence the caller should verify the signature and possibly the certification path

Why this priority

  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.3% (top 78%)
CISA exploited listNo
WeaknessCWE-295, CWE-345
Published2019-06-12
Last modified2026-06-17
Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

redhat keycloak UPGRADE
Affected: < 6.0.2
Fixed in: 6.0.2
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy keycloak || rpm -q keycloak || keycloak --version
2. UPGRADE to 6.0.2 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade keycloak
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade keycloak
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
redhat single sign-on DOWNGRADE
Affected: 7.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.3
1. Check installed version
apt-cache policy single-sign-on || rpm -q single-sign-on || single-sign-on --version
2. No fixed release: DOWNGRADE to a release before 7.3 (Debian / Ubuntu)
apt-cache madison single-sign-on sudo apt install single-sign-on=<VERSION_BEFORE_7.3> sudo apt-mark hold single-sign-on
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list single-sign-on sudo dnf downgrade single-sign-on-<VERSION_BEFORE_7.3> sudo dnf versionlock add single-sign-on
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-3875?

keycloak: upgrade to 6.0.2; single sign-on: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2019-3875 being exploited?

CVE-2019-3875 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-3875 affect?

CVE-2019-3875 affects keycloak, single sign-on. Severity is medium (CVSS 6.5). A vulnerability was found in keycloak before 6.0.2. The X.509 authenticator supports the verification of client certificates through the CRL, where the CRL list can be obtained from the URL provided in the certificate itself (CDP) or throug

How urgent is CVE-2019-3875?

Priority 38/100. Remotely exploitable, no login, no user action; On your watchlist

Software pages

Keycloak vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.