Keycloak Services has a potential bypass of brute force protection

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-4629: 0.79% estimated exploitation activity in the next 30 days; percentile 56.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

If an attacker launches many login attempts in parallel then the attacker can have more guesses at a password than the brute force protection configuration permits. This is due to the brute force check occurring before the brute force protector has locked the user. Acknowledgements: Special thanks to Maurizio Agazzini for reporting this issue and helping us improve our project.

Published by the source

17 Sep 2024, 22:29 UTC

Last modified by the source

17 Sep 2024, 22:29 UTC

Source last checked

26 Oct 2026, 16:31 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gc7q-jgjv-vjr2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-4629

Advisory: Keycloak Services has a potential bypass of brute force protection
IDs: CVE-2024-4629, GHSA-gc7q-jgjv-vjr2
Record: https://patchnext.com/advisories/cve-2024-4629 (revision 1, source checked 26 Oct 2026, 16:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.keycloak:keycloak-services 25.0.4, 24.0.7, 22.0.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.keycloak:keycloak-services: affected < 22.0.12; >= 23.0.0, < 24.0.7; >= 25.0.0, < 25.0.4; fixed in 24.0.7, 22.0.12, 25.0.4

## Suggested inspection (read-only)
- Maven org.keycloak:keycloak-services: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.keycloak:keycloak-services.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gc7q-jgjv-vjr2 (GitHub-reviewed advisory GHSA-gc7q-jgjv-vjr2 lists affected ranges: Maven org.keycloak:keycloak-services >=0 =23.0.0 =25.0.0 <25.0.4)

Commands are suggestions: review each one before running it.