CVE-2026-87853: Sssd: sssd: idp authentication prefix comparison allows cross-user impersonation

Published Sep 9, 2026
·
Updated

A flaw was found in SSSD's IdP authentication provider. The evalaccesstokenbuf() function compares the OIDC subject identifier using strncmp() with the authenticated user's identifier length, performing a prefix comparison instead of an exact match. An attacker whose IdP identifier is a strict prefix of a target user's identifier can authenticate as the target user.

Other sources

A flaw was found in SSSD's IdP authentication provider. The evalaccesstokenbuf() function in src/providers/idp/idpautheval.c compares the authenticated user's OIDC subject identifier against the requested user's stored SYSDBUUID using strncmp() with the authenticated identifier's length as the count. This performs a prefix comparison rather than an exact match. An attacker whose complete IdP identifier is a strict prefix of a target user's identifier can authenticate as the target, gaining full access to the target's account, files, groups, and local authorization. With Keycloak's built-in LDAP provider (Import Users disabled), the identifier format f:<federationid>:<username> naturally produces prefix relationships for usernames like 'admin' and 'administrator'. No victim credential, interaction, or administrative role is required.

Red Hat

Affected Software

1 affected component
sssd>=<=

Event History

Sep 9, 2026
Data Sourced
via Red Hat·01:13 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·04:06 PM
Data Sourced
via MITRE·04:06 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is most likely to be exposed to this issue?

Systems using SSSD's IdP authentication provider are exposed when one user's OIDC subject identifier is a strict prefix of another user's identifier. Keycloak deployments using the built-in LDAP provider with Import Users disabled can naturally create this condition for usernames such as "admin" and "administrator".

2

What does an attacker need to exploit the flaw?

The attacker needs a valid IdP identity whose complete identifier is a strict prefix of the target user's identifier, and the ability to authenticate through the affected SSSD IdP provider. No victim credentials or user interaction are required.

3

What access can successful exploitation provide?

A successful attacker can authenticate as the target user and gain that account's access, including its files, groups, and local authorization.

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