LiveActive security incident?Get immediate response
CVE Record

CVE-2026-9791: Keycloak-rhel9: organization data leak after feature disabled in keycloak

A flaw was found in Keycloak. An authenticated user with existing organization membership can exploit this flaw by accessing user-facing APIs, such as the account API or by requesting an OpenID Connect (OIDC) token with the 'organization' scope. This allows organization metadata to be disclosed in tokens, even after an administrator has explicitly disabled the Organizations feature, potentially leading to incorrect authorization decisions by resource servers.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Keycloak may continue exposing organization metadata after the Organizations feature is disabled. The issue requires an authenticated user who already has organization membership. Business risk is mainly incorrect downstream authorization if applications trust organization claims that should no longer be available.

Executive priority

Treat this as a moderate identity-platform fix. It is not described as actively exploited, but authorization decisions based on stale organization data can create business access-control risk across dependent applications.

Technical view

CVE-2026-9791 is a CWE-863 authorization flaw in Red Hat build of Keycloak. Account APIs and OIDC tokens requested with the organization scope can disclose organization metadata after the feature is disabled. CVSS is 4.3, with low confidentiality impact and no integrity or availability impact stated.

Likely exposure

Exposure is limited to Red Hat build of Keycloak 26.4 and 26.6 packages listed as affected, especially deployments using Organizations, account APIs, OIDC organization scope, or resource servers that authorize based on organization claims.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. Abuse requires an authenticated user with existing organization membership. The main concern is data leakage in tokens or APIs and downstream services making authorization decisions from stale organization metadata.

Researcher notes

Focus assessment on affected RHBK 26.4 and 26.6 packages, organization membership state, token contents, and user-facing account APIs. Evidence supports confidentiality exposure and possible authorization side effects, but not broader product impact or public exploitation.

Mitigation direction

  • Apply the relevant Red Hat errata for affected Keycloak 26.4 or 26.6 deployments.
  • Upgrade to vendor-listed unaffected builds, such as 26.4.13 or 26.6.3 where applicable.
  • Review resource servers that trust organization claims for authorization decisions.
  • Check Red Hat guidance before relying on feature disablement as a compensating control.

Validation and detection

  • Inventory Red Hat build of Keycloak versions and package names across environments.
  • Confirm whether Organizations was enabled and later disabled in any realm.
  • Review clients requesting the OIDC organization scope.
  • Check whether account APIs expose organization metadata to authenticated members.
  • Verify upgraded environments no longer disclose disabled organization metadata.
Prepared
Confidence
high
Sources
8

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 · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-9791 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.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
7Source 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.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N2.81.4redhat

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-9791Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-operator-bundle, 26.4.13-1affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9, 26.4-19affected
Red HatRed Hat build of Keycloak 26.4rhbk/keycloak-rhel9-operator, 26.4-19affected
Red HatRed Hat build of Keycloak 26.4.13rhbk/keycloak-rhel9unaffected
Red HatRed Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle, 26.6.3-3affected
Red HatRed Hat build of Keycloak 26.6rhbk/keycloak-rhel9, 26.6-6affected
Red HatRed Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator, 26.6-6affected
Red HatRed Hat build of Keycloak 26.6.3rhbk/keycloak-rhel9unaffected
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.