CVE-2026-0871: Org.keycloak/keycloak-services: keycloak: unauthorized modification of unmanaged user attributes by administrators

Published Jan 13, 2026
·
Updated

A flaw was found in Keycloak. An administrator with manage-users permission can bypass the "Only administrators can view" setting for unmanaged attributes, allowing them to modify these attributes. This improper access control can lead to unauthorized changes to user profiles, even when the system is configured to restrict such modifications.

Other sources

Summary

When the Unmanaged Attributes is set to Only administrators can view, the administrator that has manage-users permission can anyway edit the unmanaged attributes. For example using curl or kcsdm.sh:

./kcadm.sh update users/b0df9d35-3319-4e87-81ea-9a906372fa1f -r sample -s "attributes.lala=lala"

Requirements to exploit

The realm should be configured unmanaged attributes to Only administrators can view and the admin should have permissions to edit users.

Component affected:

org.keycloak:keycloak-services Version affected: <26.4.0

Patch available: no

CVSS: (Based on

https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator

) Initially i would say medium:

Vector:

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N Base Score: 4.9 (Medium)

Embargo: no, if you consider it's moderate too.

Acknowledgement

Steps to reproduce

Create a new realm and configure in realm settings -> Genaral tab -> unmanaged attributes to Only administrators can view.

Use kcadm (for example to edit the user with an admin that has manage-users permission using the presented command.

The user is updated and toy can see the new attribute in the console.

The operation should an error or attributes skipped.

Red Hat

Affected Software

5 affected componentsFixes available
maven/org.keycloak/keycloak-services<26.4.0
maven/org.keycloak:keycloak-server-spi-private<26.5.2
26.5.2
redhat Build Of Keycloak<26.4.9
redhat Build Of Keycloak
redhat keycloak<26.4.0

Event History

Jan 13, 2026
Data Sourced
via Red Hat·08:35 AM
DescriptionSeverityAffected Software
Feb 27, 2026
CVE Published
via MITRE·07:30 AM
Data Sourced
via MITRE·07:30 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:17 AM
Affected Software
Advisory Published
via GitHub·09:30 AM
Data Sourced
via GitHub·09:30 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-0871?

CVE-2026-0871 is considered a critical vulnerability due to its potential for unauthorized modifications of unmanaged user attributes by administrators.

2

How do I fix CVE-2026-0871?

To fix CVE-2026-0871, upgrade to Keycloak version 26.5.2 or later.

3

Who is affected by CVE-2026-0871?

CVE-2026-0871 affects Keycloak versions up to 26.4.0 including specific builds by Red Hat.

4

What causes CVE-2026-0871?

CVE-2026-0871 is caused by insufficient restrictions on administrator permissions regarding unmanaged user attributes.

5

Can CVE-2026-0871 lead to data breaches?

Yes, CVE-2026-0871 can lead to data breaches due to unauthorized access to sensitive user attributes by administrators.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203