# CVE-2026-92821: Sssd: sssd: access control bypass via premature ldap access rule evaluation

> Authenticated users with expired passwords can bypass access controls in SSSD when password expiration warnings are evaluated before restrictive LDAP rules.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-92821, GHSA-3hrm-ww2w-wqqc, UBUNTU-CVE-2026-92821

## What is CVE-2026-92821?

CVE-2026-92821 is a medium-severity authentication bypass vulnerability in Red Hat Enterprise Linux 10, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-393 (Return of Wrong Status Code)

## Which versions are affected by CVE-2026-92821?


## How do I fix CVE-2026-92821?

No fix has been published for CVE-2026-92821 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92821 being exploited?

There is no known exploitation of CVE-2026-92821 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92821 and fix it if it is affected.

What it is: CVE-2026-92821 is a medium-severity authentication bypass vulnerability in Red Hat Enterprise Linux 10, published on 6 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-92821 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92821/ (Markdown: https://insights.sbomify.com/CVE-2026-92821/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92821
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92821
- OSV: https://osv.dev/vulnerability/CVE-2026-92821

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92821/
Summaries are generated and may contain mistakes; the official description above is the record.