CVE-2026-104038

Sssd: sssd: denial of service via missing sid extension in certificate mapping

  • Medium 5.9

Description

A flaw was found in sssd. A remote attacker can cause a denial of service (DoS) by submitting a certificate that lacks an expected Security Identifier (SID) extension. In deployments configured with SID-based certificate mapping rules, the service fails to verify the presence of the extension before processing it, causing the process to crash during authentication or lookup operations.

Key facts

Published
6 Oct 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.267% likely to be exploited in the next 30 days, higher than 19% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.9CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

What to do

  • A configuration-based workaround is available. Until a fix is shipped, avoid SSSD certificate mapping rules whose LDAPU1 maprule expands the {sid} or {sid.rid} templates (for example, 'maprule = LDAPU1:(objectsid={sid.rid})'). If SID-based mapping is required, reject certificates that lack the Microsoft SID extension (OID 1.3.6.1.4.1.311.25.2) before they reach the affected certificate mapping evaluation path, so SID-based rules fail cleanly instead of crashing the service.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