Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2020-14389 — keycloak-core

HIGH

CVE-2020-14389 is a high-severity (CVSS 8.1) CWE-916 vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

Improper privilege management in Keycloak

Also known asGHSA-c9x9-xv66-xp3v
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 10, 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 CVEs56th percentile — riskier than 56% 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

CVE-2020-14389 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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, where it would permit a user with a view-profile role to manage the resources in the new account console. This flaw allows a user with a view-profile role to access and modify data for which the user does not have adequate permission.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-coreall versions12.0.0org.keycloak:keycloak-core:12.0.0

Affected Products

1 product · 1 configurations
Application
keycloakredhat
< 12.0.0
range

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 12.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-14389 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatModerate
ProductFixed inAdvisory
Red Hat Single Sign-On 7.4.3see advisoryRHSA-2020:4931
Red Hat Single Sign-On 7.4 for RHEL 6rh-sso7-keycloak-0:9.0.9-1.redhat_00001.1.el6ssoRHSA-2020:4929
Red Hat Single Sign-On 7.4 for RHEL 7rh-sso7-keycloak-0:9.0.9-1.redhat_00001.1.el7ssoRHSA-2020:4930
Red Hat Single Sign-On 7.4 for RHEL 8rh-sso7-keycloak-0:9.0.9-1.redhat_00001.1.el8ssoRHSA-2020:4932

Frequently Asked Questions

A flaw was found in Keycloak, where it would permit a user with a view-profile role to manage the resources in the new account console. This flaw allows a user with a view-profile role to access and modify data for which the user does not have adequate permission.
O3 Security · Impact-Aware SCA

Is CVE-2020-14389 in your dependencies?

Find it across Maven, including transitive dependencies.

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