GHSA-2p82-5wwr-43cw
MEDIUMGHSA-2p82-5wwr-43cw is a medium-severity (CVSS 5.4) Improper Authentication vulnerability in org.keycloak:keycloak-ldap-federation. O3 Security confirms whether GHSA-2p82-5wwr-43cw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Authentication Bypass Due to Missing LDAP Bind After Password Reset in Keycloak
Blast Radius
org.keycloak:keycloak-ldap-federation☕org.keycloak:keycloak-ldap-federationReal-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
The issue arises because Keycloak does not perform an LDAP bind after a password reset, leading to potential authentication bypass for expired or disabled AD accounts. A fix should enforce LDAP validation after password updates to ensure consistency with AD authentication policies.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.keycloak:keycloak-ldap-federation | ≥ 26.1.0&&< 26.1.3 | 26.1.3 |
| ☕Maven | org.keycloak:keycloak-ldap-federation | all versions | 26.0.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-ldap-federation. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.keycloak:keycloak-ldap-federation to 26.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p82-5wwr-43cw is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-2p82-5wwr-43cw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2p82-5wwr-43cw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2p82-5wwr-43cw in your dependencies?
O3 detects GHSA-2p82-5wwr-43cw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.