Keycloak leaks configured LDAP bind credentials through the Keycloak admin console

Exploitation

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

CVSS

2.7 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2024-5967: 0.65% estimated exploitation activity in the next 30 days; percentile 51.18 (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.

Impact The LDAP testing endpoint allows to change the Connection URL independently of and without having to re-enter the currently configured LDAP bind credentials. An attacker with admin access (permission manage-realm) can change the LDAP host URL ("Connection URL") to a machine they control. The Keycloak server will connect to the attacker's host and try to authenticate with the configured credentials, thus leaking them to the attacker. As a consequence, an attacker who has compromised the admin console/compromised a user with sufficient privileges can leak domain credentials and can now attack the domain. Acknowledgements Special thanks to Simon Wessling for reporting this issue and helping us improve our project

Published by the source

21 Jun 2024, 15:52 UTC

Last modified by the source

1 Jul 2024, 14:39 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c25h-c27q-5qpv

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

# Patch Next advisory brief: CVE-2024-5967

Advisory: Keycloak leaks configured LDAP bind credentials through the Keycloak admin console
IDs: CVE-2024-5967, GHSA-c25h-c27q-5qpv
Record: https://patchnext.com/advisories/cve-2024-5967 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.7)
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-ldap-federation 25.0.1, 24.0.6, 22.0.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.keycloak:keycloak-ldap-federation: affected >= 25.0.0, <= 25.0.0; <= 22.0.11; >= 23.0.0, <= 24.0.5; fixed in 22.0.12, 24.0.6, 25.0.1

## Suggested inspection (read-only)
- Maven org.keycloak:keycloak-ldap-federation: 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-ldap-federation.
- 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-c25h-c27q-5qpv (GitHub-reviewed advisory GHSA-c25h-c27q-5qpv lists affected ranges: Maven org.keycloak:keycloak-ldap-federation >=25.0.0 =0 =23.0.0 <=24.0.5)

Commands are suggestions: review each one before running it.