CVE-2026-104039

Sssd: sssd: denial of service via stale connection state reuse in pam gssapi responder

  • Medium 4.7

Description

A flaw was found in SSSD. A local user can cause a denial of service (DoS) by disrupting system authentication services. When handling Generic Security Services Application Programming Interface (GSSAPI) authentication in the Pluggable Authentication Module (PAM) responder, cached connection state is freed upon completion without clearing the reference pointer. An attacker can exploit this by sending an additional request over the same connection, causing the service to access invalid memory and unexpectedly terminate.

Key facts

Published
6 Oct 2026
Last changed
5 Nov 2026
Assigned by
redhat
EPSS
0.131% likely to be exploited in the next 30 days, higher than 2.773% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 4.7CVSS 3.1, Mediumfrom the CNA (redhat)CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

What to do

  • A workaround is available for this issue. PAM GSSAPI authentication can be disabled in the SSSD configuration: edit /etc/sssd/sssd.conf, and in the [pam] section remove or comment out the pam_gssapi_services option (or set it to an empty value), so that no service is permitted to use GSSAPI authentication through the PAM responder. Then restart the SSSD service (systemctl restart sssd) to apply the change. Note that disabling PAM GSSAPI authentication prevents clients from authenticating to the affected PAM services using Kerberos tickets, requiring them to use alternative authentication methods such as passwords. Restarting the SSSD service also briefly disrupts ongoing authentication requests. Restarting the PAM responder can restore service after a crash, but it does not remove the underlying flaw.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 10
  • Default status: affected
Red HatRed Hat Enterprise Linux 6
  • Default status: unknown
Red HatRed Hat Enterprise Linux 7
  • Default status: affected
Red HatRed Hat Enterprise Linux 8
  • Default status: affected
Red HatRed Hat Enterprise Linux 9
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 4
  • Default status: affected
Red HatRed Hat OpenShift Container Platform 5
  • Default status: affected

Timeline

  1. 18 May 2026 Reported to Red Hat.
  2. 6 Oct 2026 Made public.
  3. 6 Oct 2026 Published

Weakness

References