# CVE-2026-3911: Keycloak: Information disclosure of disabled user attributes via administrative endpoint

> Authenticated users with view-users role can access hidden user attributes via an administrative endpoint, exposing sensitive data.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** BIT-keycloak-2026-3911, GHSA-xh32-c9wx-phrp, MINI-368f-7h3g-gfwr, MINI-7cm2-6q72-42p5

## What is CVE-2026-3911?

CVE-2026-3911 is a low-severity vulnerability in Redhat Build of Keycloak, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A flaw was found in Keycloak. An authenticated user with the view-users role could exploit a vulnerability in the UserResource component. By accessing a specific administrative endpoint, this user could improperly retrieve user attributes that were configured to be hidden. This unauthorized information disclosure could expose sensitive user data.

Weakness: CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-3911?

3 open source packages ship an affected version, including org.keycloak:keycloak-services and keycloak. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.5.5 | None |
| `org.keycloak:keycloak-services` | Maven | All versions to 26.5.5 | None |
| `keycloak` | Bitnami | From 26.4.0 | 26.4.1, 26.5.0 |

Products: Redhat Build of Keycloak.

## How do I fix CVE-2026-3911?

Apply the vendor's patch.

## Is CVE-2026-3911 being exploited?

There is no known exploitation of CVE-2026-3911 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3911 and fix it if it is affected.

What it is: CVE-2026-3911 is a low-severity vulnerability in Redhat Build of Keycloak, published on 11 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-3911 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.5; no fix listed
- org.keycloak:keycloak-services (Maven): affected all versions up to 26.5.5; no fix listed
- keycloak (Bitnami): affected from 26.4.0; fixed in 26.4.1, 26.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3911/ (Markdown: https://insights.sbomify.com/CVE-2026-3911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3911
- OSV: https://osv.dev/vulnerability/CVE-2026-3911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3911/
Summaries are generated and may contain mistakes; the official description above is the record.