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-104040 Overview
CVE-2026-104040 is an input sanitization flaw in the System Security Services Daemon (SSSD) when configured with the Microsoft Entra ID identity provider. SSSD fails to escape single quotes in lookup names before embedding them in Microsoft Graph Open Data Protocol (OData) queries. A low-privileged local user can submit a crafted search request to alter query filters and broaden user or group lookups. The flaw maps to improper encoding or escaping of output [CWE-140] and can result in information disclosure of unintended directory objects. The same primitive enables a Denial of Service (DoS) condition through excessive backend processing and cache population.
Critical Impact
Local users can manipulate Microsoft Graph OData filters through unescaped single quotes, exposing unintended Entra ID directory data and triggering resource exhaustion in the SSSD cache.
Affected Products
- SSSD (System Security Services Daemon) configured with the Entra ID identity provider
- Red Hat Enterprise Linux distributions shipping affected SSSD builds
- Downstream Linux distributions packaging the vulnerable SSSD release
Discovery Timeline
- 2026-10-06 - CVE-2026-104040 published to the National Vulnerability Database
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-104040
Vulnerability Analysis
SSSD integrates Linux hosts with external identity providers, including Microsoft Entra ID. When resolving a user or group, SSSD constructs a Microsoft Graph OData query and embeds the requested lookup name directly into the filter expression. OData filter strings delimit literal values with single quotes, so an unescaped single quote inside a lookup name terminates the literal and allows the rest of the input to be interpreted as filter syntax.
An authenticated local user can submit a lookup name that contains a single quote followed by additional OData operators. The backend forwards the modified filter to Microsoft Graph, which returns directory objects that match the attacker-controlled predicate instead of the intended identity. The result is read-only exposure of directory attributes the caller would not otherwise retrieve.
The same injection surface also supports broad wildcard-style predicates that force Entra ID to return large result sets. SSSD then processes and caches each returned object, which consumes CPU, memory, and cache storage on the host.
Root Cause
The root cause is improper encoding of a user-controlled string before concatenation into an OData filter expression [CWE-140]. SSSD does not apply the OData literal-escaping rule, which requires each embedded single quote to be doubled. Any lookup name containing ' therefore changes the structure of the outgoing Graph query.
Attack Vector
Exploitation requires local access and low privileges. The attacker invokes a standard SSSD name-resolution interface, such as a lookup through the Name Service Switch (NSS), supplying a crafted principal name. SSSD passes the name into the Entra ID provider, where it becomes part of a Graph OData $filter clause. The injected predicate overrides the intended equality check and expands the search scope. No user interaction and no network-facing exposure are required.
No verified public proof-of-concept is available. See the Red Hat CVE-2026-104040 Advisory and the Red Hat Bug Report #2478915 for technical details.
Detection Methods for CVE-2026-104040
Indicators of Compromise
- SSSD debug logs containing lookup names with embedded single-quote characters or OData operators such as or, startswith, or eq.
- Microsoft Graph audit entries showing filter expressions returning object counts far above the single-identity norm.
- Sudden growth of the SSSD cache files under /var/lib/sss/db/ without a corresponding change in user population.
Detection Strategies
- Parse sssd_be and sssd_nss logs for lookup inputs that contain ', %27, or OData keywords, and alert on matches.
- Correlate local process execution of getent, id, or sss_cache with abnormally large Graph response sizes recorded in Entra ID sign-in and audit logs.
- Baseline normal cache file sizes per host and alert on rapid expansion that is not tied to legitimate account onboarding.
Monitoring Recommendations
- Forward /var/log/sssd/*.log to a centralized log platform and retain Entra ID Graph audit logs for correlation.
- Monitor CPU and memory consumption of the sssd_be process for sustained spikes tied to specific local users.
- Track the rate of Microsoft Graph /users and /groups queries per host to detect anomalous lookup volume.
How to Mitigate CVE-2026-104040
Immediate Actions Required
- Apply the SSSD security update from your Linux distribution as soon as patched packages are available.
- Inventory hosts configured with the Entra ID identity provider by inspecting /etc/sssd/sssd.conf for id_provider = entra_id or equivalent.
- Restrict interactive local access on affected hosts to trusted administrative users until patching is complete.
Patch Information
Monitor the Red Hat CVE-2026-104040 Advisory and the Red Hat Bug Report #2478915 for fixed package versions. Rebuild downstream SSSD packages against the patched upstream source once released, and restart the sssd service after installation to load the corrected provider code path.
Workarounds
- Where feasible, switch the SSSD identity provider to a backend other than Entra ID until a fixed package is deployed.
- Reduce the SSSD cache lifetime via the entry_cache_timeout directive to limit the persistence of attacker-retrieved objects.
- Enforce input constraints at the identity management layer so that account names containing single quotes cannot be requested through local tooling.
# Verify SSSD version and Entra ID provider configuration
rpm -q sssd
grep -E '^(id_provider|auth_provider)' /etc/sssd/sssd.conf
# Reduce cache exposure window after assessing operational impact
sudo sed -i 's/^entry_cache_timeout.*/entry_cache_timeout = 300/' /etc/sssd/sssd.conf
sudo systemctl restart sssd
# Clear any cached objects populated during suspected exploitation
sudo sss_cache -E
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

