VulnerabilityPublished 4 Nov 2026

CVE-2026-104029: sssd security update

Affects sssdSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-104029· Low 3.3

Not known to be exploited · CVSS 3.3 Low : upgrade to 2.9.4-34.oe2403sp3 when convenient.

Data as of 4 Nov 2026, 16:57 UTC

CVSS 3.1 base score

3.3Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	3.3

Patch: Available – fixed in 2.9.4-34.oe2403sp3

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 4 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade sssd to 2.9.4-34.oe2403sp3.

Affected software

Product	Affected	Fixed in
openEuler 24.03-LTS-SP3sssd`pkg:rpm/openEuler/sssd&distro=openEuler-24.03-LTS-SP3`Other threats	Affected <2.9.4-34.oe2403sp3	Fixed in 2.9.4-34.oe2403sp3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and included in SSSD version 2.9.4-34.oe2403sp3. Users should upgrade to this fixed version to remediate all identified vulnerabilities. No additional mitigation actions are indicated beyond applying the official fix.

Description

Multiple vulnerabilities have been identified in SSSD, a set of daemons managing access to remote directories and authentication mechanisms. These flaws include out-of-bounds memory reads, use-after-free conditions, missing authorization checks, and improper handling of authentication tokens. Exploitation of these vulnerabilities by local attackers can cause denial of service (DoS) conditions by crashing various SSSD responder processes or exhausting memory. Additionally, one vulnerability allows bypassing account expiration controls, enabling unauthorized access. These issues affect versions prior to 2.9.4-34.oe2403sp3 and have been addressed in that fixed release.

Impact

Local attackers can exploit these vulnerabilities to cause denial of service by crashing SSSD responder processes or exhausting memory, disrupting authentication and automount services. One vulnerability permits bypassing account expiration controls, allowing unauthorized access with valid credentials for expired accounts. The overall impact includes service disruption and potential unauthorized system access.

Summary

SSSD contains multiple security flaws affecting its autofs responder, PAM responder, Kerberos Credential Manager (KCM) responder, and account expiration enforcement. Vulnerabilities include improper buffer offset calculations leading to out-of-bounds reads and crashes (CVE-2026-104029, CVE-2026-104037, CVE-2026-104043), missing null terminators causing buffer over-reads and process crashes (CVE-2026-104030, CVE-2026-104042), memory leaks from unreleased allocations during request processing (CVE-2026-104031, CVE-2026-104035), missing authorization checks allowing repeated master automount map updates causing cache invalidation and DoS (CVE-2026-104032), failure to treat zero expiration values as expired accounts leading to authentication bypass (CVE-2026-104033), and use-after-free in KCM responder during ticket renewal causing crashes (CVE-2026-104034). These vulnerabilities allow local attackers to disrupt authentication services and potentially gain unauthorized access. The issues are fixed in SSSD version 2.9.4-34.oe2403sp3.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 16:57 UTC

Technical details

References

Community reviews

Related threats