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

GHSA-54f3-c6hg-865h keycloak-model-jpa

HIGHFix: keycloak/keycloak#15463

GHSA-54f3-c6hg-865h is a high-severity (CVSS 7.7) CWE-770 vulnerability in org.keycloak:keycloak-model-jpa. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.keycloak:keycloak-model-jpa — see the affected versions and patch details below.

Allocation of Resources Without Limits in Keycloak

Also known asCVE-2023-6563
Published
Dec 14, 2023
Updated
Feb 16, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-54f3-c6hg-865h plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
org.keycloak:keycloak-model-jpa

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

An unconstrained memory consumption vulnerability was discovered in Keycloak. It can be triggered in environments which have millions of offline tokens (> 500,000 users with each having at least 2 saved sessions). If an attacker creates two or more user sessions and then open the "consents" tab of the admin User Interface, the UI attempts to load a huge number of offline client sessions leading to excessive memory and CPU consumption which could potentially crash the entire system.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.keycloak:keycloak-model-jpaall versions21.0.0org.keycloak:keycloak-model-jpa:21.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

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-model-jpa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.keycloak:keycloak-model-jpa to 21.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-54f3-c6hg-865h 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-54f3-c6hg-865h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-54f3-c6hg-865h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 HatImportant

While this vulnerability can enable complete compromise of system availability, it is not possible to be triggered in every environment. The impact is rated as Important due to several preconditions (number of users and how many sessions each user has) which are beyond an attacker's control.

ProductFixed inAdvisory
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el7ssoRHSA-2023:7854
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el8ssoRHSA-2023:7856
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.11-2.redhat_00003.1.el9ssoRHSA-2023:7855
RHEL-8 based Middleware Containersrh-sso-7/sso76-openshift-rhel8:7.6-38RHSA-2023:7857
Single Sign-On 7.6.6rh-sso7-keycloakRHSA-2023:7858

Frequently Asked Questions

An unconstrained memory consumption vulnerability was discovered in Keycloak. It can be triggered in environments which have millions of offline tokens (> 500,000 users with each having at least 2 saved sessions). If an attacker creates two or more user sessions and then open the "consents" tab of the admin User Interface, the UI attempts to load a huge number of offline client sessions leading to excessive memory and CPU consumption which could potentially crash the entire system.
O3 Security · Impact-Aware SCA

Is GHSA-54f3-c6hg-865h in your dependencies?

O3 Security finds GHSA-54f3-c6hg-865h across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-54f3-c6hg-865h: keycloak-model-jpa | O3 Security