cve.bz

CVE-2026-104045

4.7 mediumExploit referenceEPSS 0.1%

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

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

Severity

CVSS 3.1

4.7 medium
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-07. 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-104045 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104045?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104045?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-104045 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-104045

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-104045](https://cve.bz/cve/badge/CVE-2026-104045.svg)](https://cve.bz/cve/CVE-2026-104045)

HTML:

<a href="https://cve.bz/cve/CVE-2026-104045"><img src="https://cve.bz/cve/badge/CVE-2026-104045.svg" alt="CVE-2026-104045"></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-104045
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moresssdno fix listedUBUNTU-CVE-2026-104045
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

This vulnerability is rated as Moderate impact for Red Hat Enterprise Linux because exploitation is limited to a local denial of service against the SSSD autofs responder and requires winning a race condition under sustained concurrent requests. In typical Red Hat deployments, the autofs responder is only active when SSSD is explicitly configured to manage automount maps. Successful exploitation does not compromise system integrity or confidentiality, and the disruption remains isolated to the autofs responder daemon.

Red Hat's mitigation

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.

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-104045.

Attack patterns (CAPEC)

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

References

Check your stackJSON