CVE-2026-104031
Sssd: sssd: denial of service via memory exhaustion in autofs responder
- Medium 5.5
Description
A flaw was found in SSSD. In configurations where the autofs responder service is enabled, memory allocated during successful request processing is not released until the client connection terminates. A local attacker can exploit this vulnerability by maintaining an open connection and repeatedly submitting valid requests, leading to memory exhaustion and a Denial of Service (DoS).
Key facts
- Published
- 6 Oct 2026
- Last changed
- 5 Nov 2026
- Assigned by
- redhat
- EPSS
- 0.096% likely to be exploited in the next 30 days, higher than 0.7% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 5.5CVSS 3.1, Mediumfrom the CNA (redhat)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
What to do
- Disable the SSSD autofs responder if automount maps are not served through SSSD in your environment. To stop and disable the socket-activated autofs responder, run: # systemctl stop sssd-autofs.socket sssd-autofs.service # systemctl mask sssd-autofs.socket If the autofs responder is explicitly configured in /etc/sssd/sssd.conf, remove autofs from the services line and restart SSSD. If the responder must remain enabled, restrict access to the autofs responder socket to trusted local clients only. Closing long-lived client connections or restarting the responder reclaims the retained memory, but this is operational containment rather than a complete fix. Note that disabling the autofs responder prevents the resolution and mounting of automount maps managed via SSSD, and stopping or restarting SSSD services will briefly interrupt active identity lookups and automount operations.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.
- 5 Oct 2026 Made public.
- 6 Oct 2026 Published