Skip to content
statance
MenuClose
Log inStart for free ↗
medium · CVSS 5.4

CVE-2026-90462

Sssd: sssd: fail-open in ldap ppolicy access check allows continued authorization

Published 22 Sept 2026 · Source updated 6 Nov 2026 · Retrieved 2026-11-06 01:53 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

A flaw was found in SSSD. When configured with the LDAP access provider and `ldap_access_order` including `ppolicy` or `lockout`, a fail-open condition in the LDAP ppolicy access check can occur if a user lookup returns zero results. This can incorrectly return success and cache an allow decision, permitting continued authorization for a deleted or deprovisioned user. A remote attacker with prior valid account context could exploit this to maintain access to information and potentially make limited modifications to resources that should no longer be available.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
sssdRed HatDefault status: affectedSee vendor advisory
sssdRed HatDefault status: unknownSee vendor advisory
sssdRed HatDefault status: affectedSee vendor advisory
sssdRed HatDefault status: affectedSee vendor advisory
sssdRed HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-8Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory
openshift/ose-rhel-coreos-9Red HatDefault status: affectedSee vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed