Quick answers
- Is CVE-2026-104031 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104031 being exploited in the wild.
- How severe is CVE-2026-104031?
- Medium severity, with a CVSS score of 5.5, published 6 October 2026.
- Which products and versions are affected?
- SSSD Project SSSD.
- Is there a fix for CVE-2026-104031?
- No fixed version is recorded yet. Disable the autofs responder service if automount integration is not required, since the component is not enabled by default on standard RHEL systems.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-104031 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-104031?
- Check whether you run SSSD Project SSSD. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Disable the autofs responder service if automount integration is not required, since the component is not enabled by default on standard RHEL systems.</anigation> </invoke>
Technical details
A memory leak exists in SSSD's autofs responder where memory is not released until the client connection terminates, allowing a local attacker with low privileges to maintain an open connection and repeatedly submit valid requests to exhaust available memory. The vulnerability is classified as CWE-772 (Missing Release of Resource after Effective Lifetime) and requires local access to the autofs responder socket. The impact is confined to availability of the responder service with no compromise to confidentiality or integrity.
Affected products
- SSSD Project SSSD
Timeline
- 2026-10-06: disclosed