Vulnerabilities

Vulnerability · CVE-2017-12159

It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session.

Published Oct 26, 2017 · catalog updated Jun 17, 2026 · single sign on

Last checked Nov 6, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2017-12159. EPSS is 2.71%. Act only if a listed version of single sign on is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
2.71%
Remediation
Advisory link
Affected products
cpe keycloak/keycloak · cpe redhat/single sign on

It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe keycloak/keycloakversion unspecified
  • cpe redhat/single sign on7.0
  • cpe redhat/single sign on7.1

How to fix CVE-2017-12159

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2017-12159. EPSS is 2.71%. Act only if a listed version of single sign on is installed.

Which versions are affected?

Compare what you have installed with redhat/single sign on 7.0; redhat/single sign on 7.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-613: Insufficient Session Expiration. EPSS 2.71%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 26, 2017 · Monitored products — high

    Detected

    It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.

  2. Jun 17, 2026 · Monitored products — high

    Updated

    It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.

Sources

  • CVE.orgVulnerability recordCVE-2017-12159

    Official CVE identifier

    cve.org
  • Monitored products — highVendor advisoryCVE-2017-12159

    It was found that the cookie used for CSRF prevention in Keycloak was not unique to each session. An attacker could use this flaw to gain access to an authenticated user session, leading to possible information disclosure or further attacks.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Nov 6, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • CVE.orgNov 4, 2026
  • Monitored products — highNov 3, 2026