Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-104035Sssd: sssd: denial of service via memory exhaustion in kcm responder

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.

Timeline

  1. ID reserved

    By redhat

  2. · 5 days later

    Published

  3. · 30 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-104035, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Undergoing Analysis3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

What to do

Workaround: 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.

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-104035 badge
[![CVE-2026-104035](https://cveledger.app/badge/CVE-2026-104035.svg)](https://cveledger.app/cve/CVE-2026-104035)

Record last updated .