Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as local user with renewable TGT
-
DeliveryTrigger TGT renewal via KCM
-
ExploitHit use-after-free in deferred callback
-
ExecutionCrash KCM responder service
-
ImpactDeny Kerberos credential services (DoS)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Expired pointer prevention
|
| Exploitation Conditions | Exploitation requires that the host be explicitly configured for SSSD KCM credential renewal (KCM renewal mode) - this is the exact feature-dependent prerequisite stated in the description and is not a universal default. The attacker must be an authenticated local user (PR:L) holding a renewable Kerberos ticket-granting ticket, and must induce TGT renewal so the deferred callback fires against freed memory. Limiting factors that reduce real-world risk: local access only (AV:L, no remote vector), valid local authentication and a renewable ticket required, the non-default KCM-renewal configuration dependency, and high attack complexity (AC:H) reflecting the timing-sensitive nature of the use-after-free. Impact is confined to availability of the KCM responder; no confidentiality or integrity impact applies. |
| Impact | This is a genuinely medium/low-priority issue, consistent across signals rather than a high-CVSS-but-low-real-risk mismatch. The vendor CVSS vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H, 4.7) describes a locally-exploitable, high-complexity, authenticated flaw whose only impact is availability (A:H) with no confidentiality or integrity loss - matching the description, which limits the effect to crashing the KCM responder service (a Denial of Service). AC:H aligns with the fact that the bug is a use-after-free triggered by a deferred callback during TGT renewal, which typically depends on timing/ordering rather than a deterministic single request. No EPSS score, KEV listing, or POC indicator was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; absence of these signals is expected for a freshly-disclosed local DoS and should not be read as either safety or risk. The practical risk is bounded: an attacker must already be an authenticated local user with a renewable Kerberos ticket on a host specifically configured for KCM renewal, and the payoff is only a service crash, not code execution or data exposure. Note the description says the service crashes but does not state whether it auto-restarts; the real-world impact depends on that behavior, which is not confirmed in the provided data - verify with the Red Hat advisory. |
| Exploit ScenarioDerived | An authenticated local user on a RHEL host that has SSSD KCM renewal enabled holds a renewable Kerberos TGT and drives ticket renewal in a way that triggers the deferred callback to access already-freed memory. The use-after-free crashes the KCM responder, denying Kerberos credential-cache services to all local users until the service recovers. No public exploit code was identified at time of analysis, and the high attack complexity (AC:H) implies the trigger is timing-dependent rather than trivially reliable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
The SSSD Kerberos Credential Manager (KCM) responder can be crashed by an authenticated local user who holds a renewable Kerberos ticket-granting ticket, because a deferred callback in the TGT renewal path dereferences memory that has already been freed. Exploitation is conditional on the host being explicitly configured for KCM-based credential renewal (a non-default, feature-dependent prerequisite), and the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (4.7) reflects local access, high attack complexity, and an availability-only impact confined to the sssd-kcm service. There is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV); overall this is a medium/low-priority denial-of-service issue rather than a high-CVSS/low-real-risk outlier.
RemediationAI
No vendor-released patch version is identified in the available intelligence for CVE-2026-104034, so the first action is to monitor the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-104034 and Red Hat Bugzilla 2479178 and apply the updated sssd packages (which include sssd-kcm) as soon as an errata is published for each affected RHEL stream and for OpenShift Container Platform 4 nodes. Where immediate patching is not possible, the most effective compensating control is to remove the exposed code path by moving clients off the KCM credential cache to the KEYRING or FILE cache type, with the trade-off that cross-session/session-container ticket sharing and KCM-specific renewal behavior are lost. If KCM must remain in use, disabling renewal for the affected realm or principal (for example by issuing tickets with a renewal lifetime of zero) prevents the renewal callback from ever firing, at the cost of users having to re-authenticate when tickets expire. Additional hardening includes restricting which local accounts may obtain renewable TGTs, monitoring for repeated sssd-kcm restarts or crash dumps as an indicator of attempted triggering, and configuring systemd to restart the responder automatically so that the denial of service is brief; note that restarting KCM can invalidate tickets held in the KCM cache, so FILE/KEYRING caches should be used for critical unattended workloads. Kerberos keytabs and service principals used in headless automation are unaffected in confidentiality or integrity terms, since the flaw is availability-only.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected component is the KCM responder shipped with SSSD (sssd-kcm), the service that implements the Kerberos Credential Manager credential-cache protocol so that Kerberos tickets can be shared across sessions and containers on a host. When a credential cache is backed by KCM and the ticket carries a renew lifetime, the responder schedules renewal of the ticket-granting ticket using SSSD's asynchronous event/deferred-callback machinery. The root cause maps to CWE-825 (Expired Pointer Dereference): during the renewal flow a memory structure associated with the credential is released, but a deferred callback subsequently fires against that freed pointer, producing a use-after-free that terminates the responder process. Because the fault is timing-sensitive and depends on the order in which the deferred callback is dispatched relative to the free, it is characterized as high attack complexity (AC:H). The flaw is an availability defect only: it does not expose ticket contents, key material, or allow code execution, so C/I remain unaffected (C:N/I:N/A:H). CPE data associates the issue with SSSD as distributed in Red Hat Enterprise Linux 6, 7, 8, 9 and 10 and in Red Hat OpenShift Container Platform 4, reflecting that the same SSSD/KCM code is present across those platform generations rather than a single product build.
Know when Sssd gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Local-only trigger (AV:L) by an authenticated user with a renewable ticket (PR:L), timing-dependent use-after-free (AC:H), impacting only service availability (A:H; C/I:N).
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in SSSD. A use-after-free vulnerability exists in the Kerberos Credential Manager (KCM) responder during Kerberos ticket-granting ticket (TGT) renewal, where a deferred callback accesses memory that has already been released. An authenticated local user with a renewable Kerberos ticket can trigger this issue on systems configured with KCM renewal, causing the KCM responder service to crash and resulting in a Denial of Service (DoS).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Affected Products (CPE)CVE.org
Related Vulnerabilities in SSSD Multiple Security Flaws
View all 15A flaw was found in SSSD, where the sssctl command was vulnerable to shell command injection via the logs-fetch and cach
Access-control bypass in SSSD lets an already-authenticated user from a trusted identity domain reach hosts and services
The UNIX pipe which sudo uses to contact SSSD and read the available sudo rules from SSSD has too wide permissions, whic
Memory leak in the Privilege Attribute Certificate (PAC) responder plugin (sssd_pac_plugin.so) in System Security Servic
Memory exhaustion in the SSSD (System Security Services Daemon) can be triggered by an unauthenticated local attacker wh
Local unprivileged users on hosts running the System Security Services Daemon (SSSD) can crash or destabilize the NSS re
A local denial-of-service flaw in SSSD (System Security Services Daemon) lets an attacker who can connect to the PAM res
EUVD-2026-92891
GHSA-fcpm-98rx-c93x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB