# CVE-2026-104033: Sssd: sssd: access control bypass via improper ldap shadow expiration check

> Attackers with valid credentials for expired accounts can bypass access controls and authenticate to systems using SSSD with LDAP shadow expiration enabled.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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-104033, GHSA-v9m6-j2qm-86p2, UBUNTU-CVE-2026-104033

## What is CVE-2026-104033?

CVE-2026-104033 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 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.

Weakness: CWE-193 (Off-by-one Error)

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


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

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

## Is CVE-2026-104033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104033 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104033 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104033 exists.

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-104033/ (Markdown: https://insights.sbomify.com/CVE-2026-104033/index.md)
```

## Sources

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

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