CVE-2026-104035

Sssd: sssd: denial of service via memory exhaustion in kcm responder

  • Medium 5.5

Description

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.

Key facts

Published
6 Oct 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.095% likely to be exploited in the next 30 days, higher than 0.656% 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

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

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 18 May 2026 Reported to Red Hat.
  2. 5 Oct 2026 Made public.
  3. 6 Oct 2026 Published

Weakness

References