cve.bz

CVE-2026-104031

5.5 mediumExploit referenceEPSS 0.10%

Medium (5.5). EPSS 0.10% estimated probability of exploitation activity in the next 30 days.

On this page
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).

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.10% (unchanged from 0.10% a week ago; 0.10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-772 Missing Release of Resource after Effective Lifetime
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-104031 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104031?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104031?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104031 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-104031

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-104031](https://cve.bz/cve/badge/CVE-2026-104031.svg)](https://cve.bz/cve/CVE-2026-104031)

HTML:

<a href="https://cve.bz/cve/CVE-2026-104031"><img src="https://cve.bz/cve/badge/CVE-2026-104031.svg" alt="CVE-2026-104031"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
fedoraproject:sssd2.12.0
redhat:openshift_container_platform4.0
redhat:enterprise_linux7.0
redhat:enterprise_linux8.0
redhat:enterprise_linux9.0
redhat:enterprise_linux10.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14sssdno fix listedDEBIAN-CVE-2026-104031
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moresssdno fix listedUBUNTU-CVE-2026-104031
SUSELinux Enterprise Server 15 SP6-LTSS, Linux Enterprise Server for SAP Applications 15 SP6sssd2.10.2-150600.3.58.1SUSE-SU-2026:5079-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this vulnerability as Moderate severity because exploitation requires local access to an active SSSD autofs responder socket, and the impact is confined to memory exhaustion without compromising system confidentiality or integrity. On standard Red Hat Enterprise Linux systems, the autofs responder is not enabled by default and is only active when automount integration is explicitly configured. An attacker must maintain an open connection and repeatedly issue valid queries to consume resources, limiting the blast radius to the availability of the responder service.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10sssdFix deferred
Red Hat Enterprise Linux 6sssdOut of support scope
Red Hat Enterprise Linux 7sssdFix deferred
Red Hat Enterprise Linux 8sssdFix deferred
Red Hat Enterprise Linux 9sssdFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-104031.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON