CVE-2026-104045
Sssd: sssd: denial of service via race condition in autofs responder
- Medium 4.7
Description
A flaw was found in SSSD. A local user can trigger a Denial of Service (DoS) by exploiting a race condition in the autofs responder between asynchronous enumeration completion and map invalidation. By repeatedly sending concurrent map enumeration and invalidation requests, an attacker can cause memory to leak, leading to excessive memory consumption that can disrupt or crash the autofs service.
Key facts
- Published
- 6 Oct 2026
- Last changed
- 5 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.125% likely to be exploited in the next 30 days, higher than 2.238% 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.
- 4.7CVSS 3.1, Mediumfrom the CNA (redhat)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
What to do
- A real workaround exists: disable the SSSD autofs responder on systems where automount map integration via SSSD is not required. 1. Stop and mask the SSSD autofs socket and service: # systemctl stop sssd-autofs.socket sssd-autofs.service # systemctl mask sssd-autofs.socket sssd-autofs.service 2. If the 'services' line in /etc/sssd/sssd.conf explicitly lists 'autofs', remove 'autofs' from the comma-separated list and restart SSSD: # systemctl restart sssd Caveats: disabling the autofs responder prevents SSSD from serving automount maps, which will disrupt automated mounting of shares or user directories managed via SSSD. Restarting the SSSD service will briefly interrupt active authentication and directory lookup operations on the system. Where the autofs responder must remain enabled, restricting local access to the responder to trusted users, where deployment policy permits, and avoiding repeated map invalidation and enumeration cycles against large maps can reduce exposure. No released package fix is currently established for this issue.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.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat Enterprise Linux 10 |
|
| Red Hat | Red Hat Enterprise Linux 6 |
|
| Red Hat | Red Hat Enterprise Linux 7 |
|
| Red Hat | Red Hat Enterprise Linux 8 |
|
| Red Hat | Red Hat Enterprise Linux 9 |
|
| Red Hat | Red Hat OpenShift Container Platform 4 |
|
| Red Hat | Red Hat OpenShift Container Platform 4 |
|
| Red Hat | Red Hat OpenShift Container Platform 5 |
|
Timeline
- 18 May 2026 Reported to Red Hat.
- 6 Oct 2026 Made public.
- 6 Oct 2026 Published