Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLocal authenticated access to host
-
DeliveryComplete GSSAPI auth via PAM responder
-
ExploitReuse same connection for another request
-
ExecutionDereference freed connection-state pointer
-
ImpactSSSD responder crashes, authentication disrupted
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Expired pointer prevention
|
| Exploitation Conditions | Requires a local, already-authenticated user (AV:L, PR:L) able to communicate with the SSSD PAM responder, and the system must be using GSSAPI authentication handled by that responder. The attacker must complete a GSSAPI authentication request and then send a further request over the same connection after its cached state has been freed. Exploitation is limited by: local access only (no remote/network path), the need for valid low-level credentials on the host, high attack complexity (AC:H) because the dangling-pointer dereference depends on request timing/sequencing over a reused connection, and the requirement that GSSAPI auth via the PAM responder is actually in use. Impact is confined to availability (crash/DoS of authentication services); no confidentiality or integrity effect. |
| Impact | This is a genuinely medium/low-priority issue rather than an urgent one. The CVSS 3.1 base score of 4.7 (Medium) is driven by availability-only impact (C:N/I:N/A:H) and is heavily constrained by three local-side factors in the vector: local attack vector (AV:L), high attack complexity (AC:H), and required privileges (PR:L), meaning an already-authenticated local user is needed. No EPSS score, SSVC decision, KEV listing, or POC was provided in the input. Red Hat is the reporting source and the only references are the Red Hat CVE page and Bugzilla, both of which currently return no public exploit detail. There is no active-exploitation signal: no public exploit identified at time of analysis. The signals are internally consistent - a local, authenticated, complexity-gated availability bug - so there is no CVSS-vs-description conflict to flag. The CWE-825 (expired/dangling pointer dereference, use-after-free on the freed connection state) crashes the SSSD responder; because SSSD mediates system authentication, the practical blast radius is a local DoS of auth services, not remote compromise or data exposure. Bottom line: patch in normal cycle; this is not a widespread-exploitation emergency. |
| Exploit ScenarioDerived | A local user who can reach the SSSD PAM responder socket performs a GSSAPI authentication over a connection, then issues an additional request on that same connection after the cached connection state has been freed. The dangling reference pointer is dereferenced, the SSSD responder accesses invalid memory and terminates, disrupting authentication for the host. No public exploit code was provided in the input, and the AC:H rating implies the triggering sequence is not trivially reliable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Denial of service in SSSD allows a local, already-authenticated user who can reach the PAM responder and complete a GSSAPI authentication request to send a follow-up request over the same connection, dereferencing freed cached connection state and terminating the service, which disrupts system authentication. Per the authoritative assessment the issue is rated CVSS 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H): it is local-only, requires valid low-level credentials on the host, and is constrained by high attack complexity because the dangling-pointer dereference depends on request timing and sequencing over a reused connection. Impact is availability-only - no confidentiality or integrity effect - and no public exploit identified at time of analysis (no CISA KEV listing and no publicly available exploit code in the provided intelligence).
RemediationAI
Patch status is not confirmed in the available data: the only references supplied are the Red Hat CVE page (https://access.redhat.com/security/cve/CVE-2026-104039) and Bugzilla tracker 2478956, and neither an SSSD fix version nor an RHSA errata identifier is present, so no vendor-released patch version can be cited - monitor those two advisories and apply the updated sssd packages as soon as Red Hat ships them. Until then, the highest-value compensating control is to disable or avoid the GSSAPI PAM authentication path where it is not needed (for example, removing the GSSAPI-based PAM module from the PAM stack for services that do not rely on Kerberos/SSO login), accepting that this breaks single-sign-on passwordless PAM authentication for those services; note that the flaw only triggers when GSSAPI auth is actually handled by the responder, so this removes the attack surface entirely. On hosts where GSSAPI logins are required, restrict which local accounts can connect to the SSSD PAM responder socket and keep untrusted interactive users off such systems, since exploitation requires a local authenticated user and control over request sequencing on a reused connection - the trade-off is coarser account provisioning and reduced multi-user flexibility. A further containment measure is to supervise the responder so a crash is self-healing rather than a sustained outage (for example, ensuring the sssd service unit restarts on failure and monitoring for repeated responder terminations), which limits availability impact but does not prevent the initial denial of service; disabling SSSD entirely in favour of local files is the most drastic workaround and sacrifices centralized identity management.
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
SSSD (System Security Services Daemon) brokers identity and authentication lookups for the host through a set of responders, one of which is the PAM responder, reachable by local processes through a restricted local (UNIX-domain) socket rather than the network. The vulnerability sits in the GSSAPI code path of that responder, where an authenticated connection's cached GSSAPI state is released when authentication completes but the corresponding reference pointer is not cleared. This is a classic expired pointer dereference (CWE-825), a use-after-free variant in which a subsequent request reusing the same connection resolves to memory that has already been freed, producing an invalid access and process termination. The CPE data ties the affected code to the SSSD shipped across Red Hat Enterprise Linux 6, 7, 8, 9 and 10, and to Red Hat OpenShift Container Platform 4, all with wildcard version ranges; because OpenShift 4 nodes run RHEL CoreOS, the same responder code is exposed in cluster node images where GSSAPI-based PAM authentication is configured. Successful exploitation yields only a crash of authentication services - there is no memory corruption primitive described that would permit code execution, disclosure, or tampering, and the high complexity rating reflects the sequencing/timing dependency on connection reuse.
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 PAM-responder socket access by an authenticated user gives AV:L/PR:L; the reuse/timing-dependent dangling-pointer trigger justifies AC:H; only a crash results, so C:N/I:N/A:H.
Primary rating from Vendor (redhat).
CVSS VectorVendor: redhat
DescriptionCVE.org
A flaw was found in SSSD. A local user can cause a denial of service (DoS) by disrupting system authentication services. When handling Generic Security Services Application Programming Interface (GSSAPI) authentication in the Pluggable Authentication Module (PAM) responder, cached connection state is freed upon completion without clearing the reference pointer. An attacker can exploit this by sending an additional request over the same connection, causing the service to access invalid memory and unexpectedly terminate.
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-92909
GHSA-6ffw-v8mm-gqgh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB