LiveActive security incident?Get immediate response
CVE Record

CVE-2024-11736: Org.keycloak:keycloak-quarkus-server: unrestricted admin use of system and environment variables

A vulnerability was found in Keycloak. Admin users may have to access sensitive server environment variables and system properties through user-configurable URLs. 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.

MediumCVSS 4.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A highly privileged Keycloak administrator may be able to expose server environment variables or Java system properties by placing supported placeholders in configurable URLs. Those values can contain credentials or other secrets. The issue threatens confidentiality but requires administrative access; the supplied CVSS score is 4.9.

Executive priority

Treat this as a prompt privileged-access and secret-exposure review, not an unauthenticated emergency. Patch affected Red Hat builds through the applicable advisory, verify administrator activity, and rotate credentials when evidence suggests exposure. Escalate if administrative accounts are shared, compromised, or insufficiently monitored.

Technical view

Keycloak URL processing expands placeholders such as environment-variable or system-property references in administrator-controlled backchannel logout or admin URLs. A privileged administrator could use this behavior to access sensitive process configuration. The supplied CVSS 3.1 vector indicates network reachability, low complexity, high privileges, no user interaction, and high confidentiality impact without integrity or availability impact.

Likely exposure

Prioritize Red Hat build of Keycloak 26.0 deployments containing the listed affected packages and versions: operator bundle 26.0.8-1, RHEL package 26.0-7, or operator 26.0-8. The bundle marks RHBK 26.0.8 and listed JBoss products unaffected. Broader upstream exposure is not established here.

Exploitation context

Successful abuse requires Keycloak administrative privileges and control of relevant URL settings. Risk is greatest where environment variables or system properties hold reusable secrets. The bundle reports no CISA KEV listing and provides no evidence of active exploitation or a public exploit.

Researcher notes

CWE-526 and the CVSS vector support a confidentiality-only exposure requiring high privileges. The supplied material identifies affected Red Hat package builds but does not establish broader upstream version boundaries, the precise disclosure channel, or active exploitation. Avoid validating with production secrets; rely on configuration review, version checks, and vendor-supported testing.

Mitigation direction

  • Apply the applicable Red Hat updates identified in RHSA-2025:0299 or RHSA-2025:0300.
  • Restrict Keycloak administrative access to authorized personnel and trusted management networks.
  • Remove unnecessary secrets from environment variables and system properties where operationally feasible.
  • Rotate potentially exposed credentials if suspicious administrator URL changes are identified.
  • Check Red Hat guidance before changing unsupported URL-processing behavior.

Validation and detection

  • Inventory Keycloak products, packages, and exact installed versions against the supplied affected list.
  • Review backchannel logout and admin URL configurations for environment or system-property placeholders.
  • Audit administrator changes to relevant URL settings around suspected exposure periods.
  • Review outbound request and application logs for anomalous destinations without exposing secret values.
  • Confirm updated package versions using the applicable Red Hat advisory.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-526: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-11736 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6redhat

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2024-11736Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. Source timelineredhat

    Reported to Red Hat.

  2. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  3. Source timelineredhat

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Unknown vendorkeycloakkeycloak, 0unaffected
Red HatRed Hat build of Keycloak 26.0rhbk/keycloak-operator-bundle, 26.0.8-1affected
Red HatRed Hat build of Keycloak 26.0rhbk/keycloak-rhel9, 26.0-7affected
Red HatRed Hat build of Keycloak 26.0rhbk/keycloak-rhel9-operator, 26.0-8affected
Red HatRHBK 26.0.8keycloak-quarkus-serverunaffected
Red HatRed Hat JBoss Enterprise Application Platform 8keycloak-quarkus-serverunaffected
Red HatRed Hat JBoss Enterprise Application Platform Expansion Packkeycloak-quarkus-serverunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-526 · source CWE mapping

Cleartext Storage of Sensitive Information in an Environment Variable

Cleartext Storage of Sensitive Information in an Environment Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.