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

CVE-2024-4629 — keycloak-services

MEDIUMFix: keycloak/keycloak@d78b307

CVE-2024-4629 is a medium-severity (CVSS 6.5) CWE-837 vulnerability in org.keycloak:keycloak-services. A fix is available for org.keycloak:keycloak-services — see the affected versions and patch details below.

Keycloak: potential bypass of brute force protection

Also known asBIT-keycloak-2024-4629GHSA-gc7q-jgjv-vjr2
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-4629.

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.43%0.86%1.29%0.4%0.8%May 26Sep 26Nov 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

3 pkgs affected
☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services☕org.keycloak:keycloak-services

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 vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-servicesall versions22.0.12org.keycloak:keycloak-services:22.0.12
☕Mavenorg.keycloak:keycloak-services≥ 23.0.0&&< 24.0.724.0.7org.keycloak:keycloak-services:24.0.7
☕Mavenorg.keycloak:keycloak-services≥ 25.0.0&&< 25.0.425.0.4org.keycloak:keycloak-services:25.0.4

Affected Products

7 products · 12 configurations
Application
build of keycloakredhat
≥ 22.0 && < 22.012
range
Application
keycloakredhat
< 24.0.3
range
Application
openshift container platformredhat
2 versions
4.114.12
Application
openshift container platform for linuxoneredhat
2 versions
4.94.10
Application
openshift container platform for powerredhat
2 versions
4.94.10
Application
openshift container platform ibm z systemsredhat
2 versions
4.94.10

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

  2. Fix

    Update org.keycloak:keycloak-services to 22.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-4629 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 HatLow

This vulnerability is classified as low severity due to its potential impact on account security in Keycloak environments. By exploiting the timing between login attempts and the application of brute force protection, attackers can circumvent lockout mechanisms intended to prevent multiple failed authentication…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-4629 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Build of Keycloakorg.keycloak-keycloak-parentRHSA-2024:6501
Red Hat build of Keycloak 22rhbk/keycloak-operator-bundle:22.0.12-1RHSA-2024:6500
Red Hat Single Sign-On 7org.keycloak-keycloak-parentRHSA-2024:6499
Red Hat Single Sign-On 7.6 for RHEL 7rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el7ssoRHSA-2024:6493
Red Hat Single Sign-On 7.6 for RHEL 8rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el8ssoRHSA-2024:6494
Red Hat Single Sign-On 7.6 for RHEL 9rh-sso7-keycloak-0:18.0.16-1.redhat_00001.1.el9ssoRHSA-2024:6495
RHEL-8 based Middleware Containersrh-sso-7/sso76-openshift-rhel8:7.6-52RHSA-2024:6497

Frequently Asked Questions

A vulnerability was found in Keycloak. This flaw allows attackers to bypass brute force protection by exploiting the timing of login attempts. By initiating multiple login requests simultaneously, attackers can exceed the configured limits for failed attempts before the system locks them out. This timing loophole enables attackers to make more guesses at passwords than intended, potentially compromising account security on affected systems.
O3 Security · Impact-Aware SCA

Is CVE-2024-4629 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2024-4629: keycloak-services — Fixed in 22.0.12