CVE-2026-92821

Sssd: sssd: access control bypass via premature ldap access rule evaluation

  • Medium 6.8

Description

A flaw was found in SSSD. When configured to evaluate password expiration warnings before restrictive access rules in LDAP (Lightweight Directory Access Protocol) environments, an expired-password warning terminates rule evaluation early and treats the access request as successful. A remote authenticated user with an expired password using an alternative authentication method, such as SSH public key authentication, can exploit this flaw to bypass access control restrictions and gain unauthorized access to protected systems.

Key facts

Published
6 Oct 2026
Last changed
6 Nov 2026
Assigned by
redhat
EPSS
0.31% likely to be exploited in the next 30 days, higher than 24.254% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: total

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.8CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

What to do

  • The exposure can be removed by reordering the SSSD LDAP access rules without waiting for a package update. In the affected domain section of /etc/sssd/sssd.conf, set ldap_access_order so that restrictive rules such as filter, host, and rhost are evaluated before pwd_expire_policy_warn (for example, change `ldap_access_order = pwd_expire_policy_warn, filter, host` to `ldap_access_order = filter, host, pwd_expire_policy_warn`). Alternatively, replace pwd_expire_policy_warn with pwd_expire_policy_reject where accounts with expired passwords should not continue through the access chain. Restart the SSSD service (systemctl restart sssd) to apply the change. Note that restarting SSSD briefly interrupts active authentication requests and identity lookups, and switching to pwd_expire_policy_reject changes behavior so that users with expired passwords are denied instead of warned.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 18 May 2026 Reported to Red Hat.
  2. 5 Oct 2026 Made public.
  3. 6 Oct 2026 Published

Weakness

References