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

GHSA-f4v7-3mww-9gc2

MEDIUMFix: keycloak/keycloak@7a76858

GHSA-f4v7-3mww-9gc2 is a medium-severity (CVSS 4.9) CWE-526 vulnerability in org.keycloak:keycloak-quarkus-server. O3 Security confirms whether GHSA-f4v7-3mww-9gc2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Keycloak allows unrestricted admin use of system and environment variables

Also known asCVE-2024-11736
Published
Jan 13, 2025
Updated
Feb 4, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected
org.keycloak:keycloak-quarkus-server

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 security vulnerability has been identified that allows admin users to access sensitive server environment variables and system properties through user-configurable URLs. Specifically, when configuring backchannel logout URLs or admin URLs, admin users can include placeholders like ${env.VARNAME} or ${PROPNAME}. The server replaces these placeholders with the actual values of environment variables or system properties during URL processing.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.keycloak:keycloak-quarkus-serverall versions26.0.8

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-quarkus-server. 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-quarkus-server to 26.0.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4v7-3mww-9gc2 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-f4v7-3mww-9gc2 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-f4v7-3mww-9gc2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A security vulnerability has been identified that allows admin users to access sensitive server environment variables and system properties through user-configurable URLs. Specifically, when configuring backchannel logout URLs or admin URLs, admin users can include placeholders like ${env.VARNAME} or ${PROPNAME}. The server replaces these placeholders with the actual values of environment variables or system properties during URL processing.
O3 Security · Impact-Aware SCA

Is GHSA-f4v7-3mww-9gc2 in your dependencies?

O3 detects GHSA-f4v7-3mww-9gc2 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.