CVE-2026-12610 | Sssd: use-after-free crash in sssd' 'sssd_pam' process

A flaw was found in sssd. When authenticating with a YubiKey, the SSSD PAM responder can crash due to a use-after-free vulnerability, where a memory pointer is incorrectly handled. A local attacker could exploit this flaw by manipulating smartcard or YubiKey contents, leading to a denial of service that disrupts authentication. This vulnerability also presents a potential for privilege escalation, although it is difficult to exploit.

Published: 2026-06-30 Last update: 2026-06-30 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-12610 is rated Low Risk (27.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.16%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-12610

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-30 — 0.16% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-12610

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.4 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.5 5.9 [email protected]

Weakness enumeration for CVE-2026-12610

GitHub Security Advisory for CVE-2026-12610

GHSA-f953-7679-xc38 · Severity: medium — A flaw was found in sssd. When authenticating with a YubiKey, the SSSD PAM responder can crash...

OS Trackers for CVE-2026-12610

vendor priority summary link
debian not yet assigned CVE-2026-12610 not yet assigned priority: Debian including 1 source packages (sssd), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 4. https://security-tracker.debian.org/tracker/CVE-2026-12610
suse medium CVE-2026-12610 severity moderate: SUSE including 1 source package names (sssd), 1 product×package rows across 1 product lines (SUSE Linux Enterprise Server Teradata 12 SP3): Known Not Affected 1. https://www.suse.com/security/cve/CVE-2026-12610/
ubuntu medium CVE-2026-12610 medium priority: Ubuntu including 1 source packages (sssd), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, resolute, upstream, xenial): needs-triage 8. https://ubuntu.com/security/CVE-2026-12610

Affected software / configurations for CVE-2026-12610

Vendor Product Version Raw CPE
fedoraproject sssd — cpe:2.3:a:fedoraproject:sssd:-:*:*:*:*:*:*:*
redhat enterprise_linux 8.0 cpe:2.3:o:redhat:enterprise_linux:8.0:*:*:*:*:*:*:*
redhat enterprise_linux 9.0 cpe:2.3:o:redhat:enterprise_linux:9.0:*:*:*:*:*:*:*
redhat enterprise_linux 10.0 cpe:2.3:o:redhat:enterprise_linux:10.0:*:*:*:*:*:*:*

References for CVE-2026-12610

cvelogic Threat Intelligence