CVE-2026-104033

Sssd: sssd: access control bypass via improper ldap shadow expiration check

  • Medium 5.4

Description

A flaw was found in SSSD. When configured to enforce account expiration using LDAP (Lightweight Directory Access Protocol) shadow attributes, SSSD fails to treat an expiration value of zero as an expired account. A user with valid credentials for an expired account can exploit this flaw to bypass access controls and authenticate to the system. This allows unauthorized access to persist after the account was intended to be deactivated.

Key facts

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

Severity scores

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

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

What to do

  • Until a fix is available, deployments using SSSD's LDAP shadow-based expiration (access_provider = ldap with ldap_access_order including expire and ldap_account_expire_policy = shadow) should not rely on shadowExpire=0 to expire accounts. Set the shadowExpire attribute to a positive past day value so that SSSD correctly treats the account as expired, or enforce account disablement or expiration through directory-side controls that do not depend solely on this client-side SSSD check. If SSSD has cached the affected account's attributes, invalidate the cached entry (for example with sss_cache -u <username>) or restart the sssd service so the updated directory values take effect; note that restarting the service or clearing cached data can briefly interrupt active authentication sessions on the host.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