NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2020-1724 — keycloak-core

MEDIUM

CVE-2020-1724 is a medium-severity (CVSS 4.3) CWE-613 vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

Keycloak Insufficient Session Expiry

Also known asGHSA-8xj2-47xw-q78c
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 30, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk
0.00%0.44%0.88%1.32%0.1%0.8%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.keycloak:keycloak-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Keycloak in versions before 9.0.2. This flaw allows a malicious user that is currently logged in, to see the personal information of a previously logged out user in the account manager section.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-coreall versions9.0.2org.keycloak:keycloak-core:9.0.2

Affected Products

3 products · 3 configurations
Application
keycloakredhat
< 9.0.2
range
Application
openshift application runtimesredhat
all
Application
single sign-onredhat
1 version
7.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-core to 9.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1724 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow
ProductFixed inAdvisory
Red Hat Runtimes Spring Boot 2.2.6keycloakRHSA-2020:2252
Red Hat Single Sign On 7.3.8see advisoryRHSA-2020:2112
Red Hat Single Sign-On 7.3 for RHEL 6rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el6ssoRHSA-2020:2106
Red Hat Single Sign-On 7.3 for RHEL 7rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el7ssoRHSA-2020:2107
Red Hat Single Sign-On 7.3 for RHEL 8rh-sso7-keycloak-0:4.8.20-1.Final_redhat_00001.1.el8ssoRHSA-2020:2108
Text-Only RHOARsee advisoryRHSA-2020:2905

Frequently Asked Questions

A flaw was found in Keycloak in versions before 9.0.2. This flaw allows a malicious user that is currently logged in, to see the personal information of a previously logged out user in the account manager section.
O3 Security · Impact-Aware SCA

Is CVE-2020-1724 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2020-1724: keycloak-core — Fixed in 9.0.2