cve.bz

CVE-2026-92821 Return of Wrong Status Code

6.8 mediumEPSS 0.3%

Medium (6.8). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.8 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 24th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-393 Return of Wrong Status Code
Published
Modified
NVD analysis
Under analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-92821 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92821?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92821?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92821 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13sssdno fix listedDEBIAN-CVE-2026-92821
Debian14sssd2.13.1-5DEBIAN-CVE-2026-92821
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moresssdno fix listedUBUNTU-CVE-2026-92821
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6sssd2.10.2-150600.3.58.1SUSE-SU-2026:5079-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because successful exploitation requires a specific non-default configuration where `pwd_expire_policy_warn` is ordered ahead of restrictive rules in `ldap_access_order`, combined with a valid user account possessing an expired password. In default Red Hat Enterprise Linux configurations, this access evaluation sequence is not configured, which minimizes typical exposure. While the flaw permits an authenticated user to bypass host or filter restrictions using alternate authentication methods such as SSH public keys, the prerequisites prevent remote, unauthenticated access or compromise in standard installations.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10sssdFix deferred
Red Hat Enterprise Linux 6sssdOut of support scope
Red Hat Enterprise Linux 7sssdFix deferred
Red Hat Enterprise Linux 8sssdFix deferred
Red Hat Enterprise Linux 9sssdFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92821.

References

Check your stackJSON