cve.bz

CVE-2026-104035

5.5 mediumEPSS 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. An issue in the Kerberos Credential Manager (KCM) responder allows a local user to cause a Denial of Service (DoS) by maintaining a persistent connection and repeatedly storing and destroying credentials. Because the service fails to release cached objects from memory when credentials are removed, memory consumption grows continuously, ultimately exhausting available memory and rendering the service unresponsive.

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-17. 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-08. 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
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-104035 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104035?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104035?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-104035 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.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14sssdno fix listedDEBIAN-CVE-2026-104035
Ubuntu22.04:LTS, 24.04:LTS, 26.04:LTS and 4 moresssdno fix listedUBUNTU-CVE-2026-104035

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

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because exploitation is confined to a local denial-of-service condition affecting the SSSD Kerberos Credential Manager (KCM) responder without impacting data confidentiality, integrity, or elevating privileges. A local, authenticated user with access to the KCM UNIX socket can trigger unbounded memory accumulation within the responder daemon by maintaining a persistent connection while cycling credential operations. The blast radius is limited to the availability of the KCM responder process, and standard system operations or other SSSD services remain functional.

Red Hat's mitigation

This issue can only be exploited when the SSSD KCM responder is enabled and reachable by a local user, so mitigation focuses on limiting that exposure. On systems that do not require KCM credential caching, disable the KCM responder by stopping and masking the sssd-kcm socket and service:

# systemctl stop sssd-kcm.socket sssd-kcm.service

# systemctl mask sssd-kcm.socket sssd-kcm.service

Before disabling KCM, ensure an alternative Kerberos credential cache type (for example FILE: or KEYRING:) is configured in /etc/krb5.conf, because clients or system configurations that default to KCM: credential caches would otherwise lose Kerberos ticket management. On systems where KCM is required, restrict access to the KCM UNIX socket (/var/run/.heim_org.h5l.kcm-socket) to trusted local users where deployment policy permits. If abnormal memory growth is observed, closing the abusive client connection or restarting the sssd-kcm responder reclaims the retained connection-scoped memory; these are operational workarounds rather than a fix, and no released package fix is currently established.

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

Attack patterns (CAPEC)

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

References

Check your stackJSON