Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕ Maven

GHSA-gvgg-2r3r-53x7

MEDIUM

GHSA-gvgg-2r3r-53x7 is a medium-severity (CVSS 5.4) CWE-284 vulnerability in org.keycloak:keycloak-services. O3 Security confirms whether GHSA-gvgg-2r3r-53x7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Improper Authorization in Keycloak Organization Mapper Allows Unauthorized Organization Claims

Also known asCVE-2025-1391
Published
Mar 10, 2025
Updated
Mar 10, 2025
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
☕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

This vulnerability is caused by the improper mapping of users to organizations based solely on email/username patterns. The issue is limited to the token claim level, meaning the user is not truly added to the organization but may appear as such in applications relying on these claims. The risk increases in scenarios where self-registration is enabled and unrestricted, allowing an attacker to exploit the naming pattern. The issue is mitigated if admins restrict registration or use strict validation mechanisms.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.keycloak:keycloak-services≥ 26.1.0&&< 26.1.326.1.3
☕Mavenorg.keycloak:keycloak-servicesall versions26.0.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. 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.

  2. Fix

    Update org.keycloak:keycloak-services to 26.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gvgg-2r3r-53x7 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 pinpoints whether GHSA-gvgg-2r3r-53x7 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-gvgg-2r3r-53x7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This vulnerability is caused by the improper mapping of users to organizations based solely on email/username patterns. The issue is limited to the token claim level, meaning the user is not truly added to the organization but may appear as such in applications relying on these claims. The risk increases in scenarios where self-registration is enabled and unrestricted, allowing an attacker to exploit the naming pattern. The issue is mitigated if admins restrict registration or use strict validation mechanisms.
O3 Security · Impact-Aware SCA

Is GHSA-gvgg-2r3r-53x7 in your dependencies?

O3 detects GHSA-gvgg-2r3r-53x7 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works