Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2019-10201: It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures

47
This month
HIGH 8.1WATCHLISTUPGRADEDOWNGRADE

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

It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be modified. An attacker could use this flaw to impersonate other users and gain access to sensitive information.

Why this priority

  • High severity
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score8.1 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.7% (top 46%)
CISA exploited listNo
WeaknessCWE-592, CWE-347
Published2019-08-14
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.1
Fixed in: newer than 6.0.1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy keycloak || rpm -q keycloak || keycloak --version
2. UPGRADE to newer than 6.0.1 (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.0 · 7.3.3
Fixed in: no fixed release known
Safe to downgrade to: a release before 7.0
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.0 (Debian / Ubuntu)
apt-cache madison single-sign-on sudo apt install single-sign-on=<VERSION_BEFORE_7.0> 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.0> 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-10201?

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

Is CVE-2019-10201 being exploited?

CVE-2019-10201 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-10201 affect?

CVE-2019-10201 affects keycloak, single sign-on. Severity is high (CVSS 8.1). It was found that Keycloak's SAML broker, versions up to 6.0.1, did not verify missing message signatures. If an attacker modifies the SAML Response and removes the <Signature> sections, the message is still accepted, and the message can be

How urgent is CVE-2019-10201?

Priority 47/100. High severity; 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.