Quick answers
- Is CVE-2026-68743 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68743 being exploited in the wild.
- How severe is CVE-2026-68743?
- Medium severity, with a CVSS score of 5.5, published 4 August 2026.
- Which products and versions are affected?
- SSSD Project SSSD.
- Is there a fix for CVE-2026-68743?
- 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-68743 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-68743?
- Check whether you run SSSD Project SSSD. 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 vulnerability is an out-of-bounds read (CWE-125) in the extract_authtok_v1() function within SSSD's PAM responder. The function fails to validate the auth_token_length field against the remaining buffer size before processing. A local attacker who can connect to the SSSD PAM responder Unix socket can send a crafted protocol v1 request to trigger an out-of-bounds read, causing a process crash and denial of service. The stock PAM client uses protocol v3 and is unaffected; this path is only exploitable via direct socket access with a malicious v1 request.
Affected products
- SSSD Project SSSD
Timeline
- 2026-08-04: disclosed