Skip to main content
Vulnerability Database/CVE-2026-104047

CVE-2026-104047: SSSD Information Disclosure Vulnerability

CVE-2026-104047 is an information disclosure vulnerability in SSSD when using Microsoft Entra ID. Improper input sanitization allows local users to manipulate directory queries and access unauthorized data. This post covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104047 Overview

CVE-2026-104047 is an input sanitization flaw in the System Security Services Daemon (SSSD) when configured to use Microsoft Entra ID as its identity provider. Search inputs are not properly sanitized before being incorporated into directory query filters. A local user can submit a crafted lookup request that manipulates the query logic, resulting in unauthorized information disclosure from the directory.

The weakness is categorized as improper handling of a special element [CWE-140], a class commonly associated with LDAP injection. Red Hat tracks the issue in Bug Report #2478616 and the Red Hat CVE-2026-104047 Advisory.

Critical Impact

A local, authenticated user can enumerate directory objects and attributes they are not entitled to view by injecting filter syntax into SSSD lookup requests.

Affected Products

  • SSSD configured with the Microsoft Entra ID provider
  • Red Hat Enterprise Linux distributions shipping the affected SSSD build (see vendor advisory)
  • Downstream Linux distributions that package the vulnerable SSSD version

Discovery Timeline

  • 2026-10-06 - CVE-2026-104047 published to NVD
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-104047

Vulnerability Analysis

SSSD mediates identity lookups between local Linux services, such as nsswitch and PAM, and remote identity stores. When configured with the Microsoft Entra ID backend, SSSD translates lookup requests (for example, user or group name queries) into directory filter expressions.

The vulnerable code paths accept caller-controlled strings and embed them directly into the generated filter without escaping reserved metacharacters such as *, (, ), \, and NUL. An attacker who can trigger a lookup, including through standard getent style calls, can inject additional filter clauses. The injected filter runs with the privileges SSSD uses to query the directory, which typically exceed those of the local caller.

Successful exploitation allows disclosure of directory attributes and object existence information that policy would otherwise withhold. The impact scope is limited to confidentiality, integrity, and availability of directory data reachable by the SSSD service account.

Root Cause

The root cause is missing neutralization of filter metacharacters before query construction, consistent with [CWE-140] Improper Neutralization of Delimiters. The Entra ID provider path does not apply the escaping routines expected by directory filter grammar before concatenating user input into the request.

Attack Vector

Exploitation requires local access and low privileges. The attacker crafts a lookup identifier containing filter syntax and submits it through any interface that reaches SSSD, including getent passwd, id, PAM-driven logins, or sss_cache operations. No user interaction is required. The vulnerability does not grant code execution and does not allow directory modification.

See the Red Hat CVE-2026-104047 Advisory for vendor-confirmed technical details.

Detection Methods for CVE-2026-104047

Indicators of Compromise

  • SSSD domain logs in /var/log/sssd/ containing lookup names with unescaped *, (, ), or \ characters
  • Unexpected Entra ID directory query volume originating from a single local user context
  • Repeated getent, id, or sss_cache invocations with malformed identifiers in shell history or audit logs

Detection Strategies

  • Enable SSSD debug logging (debug_level = 6 or higher) on the [domain/...] section and parse generated filter strings for metacharacters embedded in user-supplied segments
  • Correlate Linux audit records (auditdexecve) for identity tools with subsequent SSSD query bursts to the Entra ID backend
  • Alert on local accounts issuing high-cardinality lookups that enumerate directory attributes beyond their normal working set

Monitoring Recommendations

  • Forward /var/log/sssd/*.log and auditd events to a centralized analytics platform for retention and correlation
  • Baseline normal SSSD lookup patterns per host and user, then alert on deviations such as wildcard-bearing queries
  • Monitor Entra ID sign-in and directory audit logs for anomalous read patterns tied to the SSSD service principal

How to Mitigate CVE-2026-104047

Immediate Actions Required

  • Apply the SSSD update referenced in the Red Hat CVE-2026-104047 Advisory as soon as it is available for your distribution
  • Inventory hosts where SSSD is configured with the Microsoft Entra ID provider and prioritize patching those systems
  • Restrict interactive and remote shell access on affected hosts to trusted administrators until patches are deployed

Patch Information

Red Hat tracks remediation in Bug Report #2478616. Consult the vendor advisory for the fixed SSSD package versions applicable to your Red Hat Enterprise Linux release and apply them through dnf update sssd once published. Downstream distributions should publish aligned package updates; validate the installed version after patching.

Workarounds

  • Where feasible, switch SSSD to an alternative identity provider that is not affected until the Entra ID provider is patched
  • Limit local login rights on affected hosts to reduce the population able to trigger lookups
  • Tighten the permissions granted to the SSSD service identity in Entra ID so that any injected query returns the minimum necessary data
bash
# Verify installed SSSD version and update once a fixed package is available
rpm -q sssd
sudo dnf update sssd sssd-common
sudo systemctl restart sssd

# Enable higher-fidelity logging to detect injection attempts
sudo sssctl debug-level 6
sudo tail -F /var/log/sssd/sssd_*.log

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.