Quick answers
- Is CVE-2026-68744 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68744 being exploited in the wild.
- How severe is CVE-2026-68744?
- Low severity, with a CVSS score of 3.3, published 4 August 2026.
- Which products and versions are affected?
- SSSD SSSD.
- Is there a fix for CVE-2026-68744?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-68744 attacked?
- It is attacked with local access, in a hosted service.
- Am I affected by CVE-2026-68744?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The sss_nss_protocol_fill_initgr() function in SSSD's NSS responder pre-allocates buffer space for all group entries in an initgroups reply but fails to shrink the packet when groups are skipped due to access control policies, leaving uninitialized heap bytes in the transmitted response. This is a use-of-uninitialized-resource vulnerability (CWE-908) triggered by local attackers who can connect to the SSSD NSS responder Unix socket. The disclosed data is limited to directory-level information and heap pointers from the sssd_nss process; sensitive credentials and authentication tokens in separate processes are not exposed. While the primary concern is heap pointer disclosure that could facilitate ASLR bypass when chained with a separate memory-corruption flaw, mitigations are currently unavailable.
Affected products
- SSSD SSSD
Timeline
- 2026-08-04: disclosed