CVE-2016-8609: It was found that the keycloak before 2.3.0 did not implement authentication flow correctly

Q: How do I fix CVE-2016-8609?

keycloak: upgrade to 2.3.0. Exact commands for each OS are on this page.

Q: Is CVE-2016-8609 being exploited?

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

Q: What does CVE-2016-8609 affect?

CVE-2016-8609 affects keycloak. Severity is low (CVSS 3.7). It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosu

Q: How urgent is CVE-2016-8609?

Priority 37/100. On your watchlist

Routine

LOW 3.7WATCHLISTUPGRADE

CVE-2016-8609 is a low-severity flaw (CVSS 3.7) affecting keycloak. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosure, or permit further possible attacks.

Why this priority

On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Weakness	CWE-384, CWE-287
Published	2018-08-01
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: redhat

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

Am I affected?

Timeline

2018-08-01 17:29 UTCPublished CVE record published
2026-06-17 00:54 UTCUpdated Record last modified

redhat keycloak UPGRADE

Affected: < 2.3.0

Fixed in: 2.3.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy keycloak || rpm -q keycloak || keycloak --version

2. UPGRADE to 2.3.0 (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.

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-2016-8609?

keycloak: upgrade to 2.3.0. Exact commands for each OS are on this page.

Is CVE-2016-8609 being exploited?

CVE-2016-8609 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-2016-8609 affect?

CVE-2016-8609 affects keycloak. Severity is low (CVSS 3.7). It was found that the keycloak before 2.3.0 did not implement authentication flow correctly. An attacker could use this flaw to construct a phishing URL, from which he could hijack the user's session. This could lead to information disclosu

How urgent is CVE-2016-8609?

Priority 37/100. On your watchlist

Software pages

Keycloak vulnerabilities

Related CVEs

CVE-2023-6927 MEDIUM 4.6 MITIGATE DOWNGRADE A flaw was found in Keycloak
CVE-2023-6563 HIGH 7.7 UPGRADE DOWNGRADE An unconstrained memory consumption vulnerability was discovered in Keycloak
CVE-2023-6291 HIGH 7.1 UPGRADE DOWNGRADE A flaw was found in the redirect_uri validation logic in Keycloak
CVE-2023-6134 MEDIUM 4.6 UPGRADE UPGRADE A flaw was found in Keycloak that prevents certain schemes in redirects, but permits them if a wildcard is app
CVE-2025-8419 MEDIUM 5.3 MITIGATE A vulnerability was found in Keycloak-services

References

← Back to latest CVEs