# CVE-2026-68744: Sssd: sssd: nss responder uninitialized heap disclosure in initgroups reply

> A local attacker can exploit an uninitialized heap disclosure in SSSD's NSS responder to read cached directory data and heap layout information.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** CLSA-2026-1788187301, CLSA-2026-1788195197, DEBIAN-CVE-2026-68744, GHSA-xxfg-88q3-gxgm, OESA-2026-3648, UBUNTU-CVE-2026-68744

## What is CVE-2026-68744?

CVE-2026-68744 is a low-severity vulnerability in Redhat Enterprise Linux, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in SSSD. The sss_nss_protocol_fill_initgr() function in the NSS responder pre-allocates reply space for all group entries but does not shrink the packet when groups are skipped, causing uninitialized heap bytes to be transmitted to the client. A local attacker can exploit this to disclose cached directory data and heap layout information from the sssd_nss process.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2026-68744?

It affects 3 products.


Products: Fedoraproject Sssd, Redhat Enterprise Linux, Redhat Openshift Container Platform.

## How do I fix CVE-2026-68744?

Apply the vendor's patch.

## Is CVE-2026-68744 being exploited?

There is no known exploitation of CVE-2026-68744 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Enterprise Linux

- [CVE-2022-4254](https://insights.sbomify.com/CVE-2022-4254/): Other in SSSD (high 8.8)
- [CVE-2012-3462](https://insights.sbomify.com/CVE-2012-3462/): Auth bypass in sssd (high 8.8)
- [CVE-2026-104048](https://insights.sbomify.com/CVE-2026-104048/): Sssd: sssd: authorization bypass via cross-domain username collision in hbac evaluation (medium 6.8)
- [CVE-2015-5292](https://insights.sbomify.com/CVE-2015-5292/): Denial of service in n/a (medium 6.8)
- [CVE-2026-12610](https://insights.sbomify.com/CVE-2026-12610/): Sssd: use-after-free crash in sssd' 'sssd_pam' process (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68744 and fix it if it is affected.

What it is: CVE-2026-68744 is a low-severity vulnerability in Redhat Enterprise Linux, published on 4 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68744 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68744/ (Markdown: https://insights.sbomify.com/CVE-2026-68744/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68744
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68744
- OSV: https://osv.dev/vulnerability/CVE-2026-68744

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68744/
Summaries are generated and may contain mistakes; the official description above is the record.