ALSA-2026:97077 (CVE-2026-12610)
Vulnerability from osv_almalinux – Published: 2026-11-10 00:00 – Updated: 2026-11-17 10:29 – Source websiteThe System Security Services Daemon (SSSD) service provides a set of daemons to manage access to remote directories and authentication mechanisms. It also provides the Name Service Switch (NSS) and the Pluggable Authentication Modules (PAM) interfaces toward the system, and a pluggable back-end system to connect to multiple different account sources.
Security Fix(es):
- sssd: out-of-bounds read in the sssd (CVE-2026-6245)
- sssd: Use-after-free crash in SSSD' 'sssd_pam' process (CVE-2026-12610)
Bug Fix(es) and Enhancement(s):
- Concurrent child processes trigger unnecessarily backtrace (JIRA:RHEL-108116)
- Performance impact with enumerate in SSSD > 2.7.3 (JIRA:RHEL-109754)
- Man page update: man sssd_krb5_localauth_plugin ? Missing disable = an2ln (JIRA:RHEL-123943)
- [RFE] SSSD PAM: Support Microsoft AD PKINIT authentication indicator (ms-pkca) for pam_gssapi_indicators_map (JIRA:RHEL-138905)
- Poor performance of
BE_REQ_INITGROUPShandling by 'sssd_be' (LDAP RFC2307, no nested groups) (JIRA:RHEL-142964) - SSSD needs to add Plasma Login Manager to the PAM services whitelist for the AD provider (JIRA:RHEL-154156)
- Detect foreign security principals in AD group members and silently ignore them (JIRA:RHEL-5049)
- [RfE] sssd_oidc: IdP client using TLS Certificate for authentication (JIRA:RHEL-83540)
- SSSD kerberos plugins export symbols which clash (JIRA:RHEL-151491)
- sssd_be segfaults with option "enumerate = true" with
id_provider=ldap(JIRA:RHEL-153036) - SSSD: LDAP backend ('sssd_be') initialization fails if DNS in unresponsive (JIRA:RHEL-172303)
- SSSD 2.13 doesn't work in offline mode, generates plenty of Permission denied errors (JIRA:RHEL-173660)
- [Regression] Cannot log in to FreeIPA account with password immediately after boot (JIRA:RHEL-173663)
- 'sssctl analyze --help' shows incorrect command in usage field (JIRA:RHEL-178180)
- Rebase SSSD for AlmaLinux 10.3 (JIRA:RHEL-183331)
- Smart card reader with pinpad fails C_Login. (CKF_PROTECTED_AUTHENTICATION_PATH not handled correctly) (JIRA:RHEL-5054)
- 'sssctl config-check' does not work correctly for "Accessing AD with a MSA" (JIRA:RHEL-111571)
- Regression in IPA + Idp authentication with keycloak (JIRA:RHEL-185008)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinux 10 Release Notes linked from the References section.
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libipa_hbac"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_autofs"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_certmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_idmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_nss_idmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_nss_idmap-devel"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "libsss_sudo"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "python3-libipa_hbac"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "python3-libsss_nss_idmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "python3-sss"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "python3-sss-murmur"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "python3-sssdconfig"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-ad"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-common"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-common-pac"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-dbus"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-idp"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-ipa"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-kcm"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-krb5"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-krb5-common"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-ldap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-nfs-idmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-passkey"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-proxy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-tools"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "AlmaLinux:10",
"name": "sssd-winbind-idmap"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.13.1-2.el10"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "The System Security Services Daemon (SSSD) service provides a set of daemons to manage access to remote directories and authentication mechanisms. It also provides the Name Service Switch (NSS) and the Pluggable Authentication Modules (PAM) interfaces toward the system, and a pluggable back-end system to connect to multiple different account sources. \n\nSecurity Fix(es): \n\n * sssd: out-of-bounds read in the sssd (CVE-2026-6245)\n * sssd: Use-after-free crash in SSSD\u0027 \u0027sssd_pam\u0027 process (CVE-2026-12610)\n\n\nBug Fix(es) and Enhancement(s): \n\n * Concurrent child processes trigger unnecessarily backtrace (JIRA:RHEL-108116)\n * Performance impact with enumerate in SSSD \u003e 2.7.3 (JIRA:RHEL-109754)\n * Man page update: man sssd_krb5_localauth_plugin ? Missing disable = an2ln (JIRA:RHEL-123943)\n * [RFE] SSSD PAM: Support Microsoft AD PKINIT authentication indicator (ms-pkca) for pam_gssapi_indicators_map (JIRA:RHEL-138905)\n * Poor performance of `BE_REQ_INITGROUPS` handling by \u0027sssd_be\u0027 (LDAP RFC2307, no nested groups) (JIRA:RHEL-142964)\n * SSSD needs to add Plasma Login Manager to the PAM services whitelist for the AD provider (JIRA:RHEL-154156)\n * Detect foreign security principals in AD group members and silently ignore them (JIRA:RHEL-5049)\n * [RfE] sssd_oidc: IdP client using TLS Certificate for authentication (JIRA:RHEL-83540)\n * SSSD kerberos plugins export symbols which clash (JIRA:RHEL-151491)\n * sssd_be segfaults with option \"enumerate = true\" with `id_provider=ldap` (JIRA:RHEL-153036)\n * SSSD: LDAP backend (\u0027sssd_be\u0027) initialization fails if DNS in unresponsive (JIRA:RHEL-172303)\n * SSSD 2.13 doesn\u0027t work in offline mode, generates plenty of Permission denied errors (JIRA:RHEL-173660)\n * [Regression] Cannot log in to FreeIPA account with password immediately after boot (JIRA:RHEL-173663)\n * \u0027sssctl analyze --help\u0027 shows incorrect command in usage field (JIRA:RHEL-178180)\n * Rebase SSSD for AlmaLinux 10.3 (JIRA:RHEL-183331)\n * Smart card reader with pinpad fails C_Login. (CKF_PROTECTED_AUTHENTICATION_PATH not handled correctly) (JIRA:RHEL-5054)\n * \u0027sssctl config-check\u0027 does not work correctly for \"Accessing AD with a MSA\" (JIRA:RHEL-111571)\n * Regression in IPA + Idp authentication with keycloak (JIRA:RHEL-185008)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. \n\nAdditional Changes: \n\nFor detailed information on changes in this release, see the AlmaLinux 10 Release Notes linked from the References section.\n",
"id": "ALSA-2026:97077",
"modified": "2026-11-17T10:29:32Z",
"published": "2026-11-10T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2026:97077"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-12610"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2026-6245"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2457954"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2490288"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/10/ALSA-2026-97077.html"
}
],
"related": [
"CVE-2026-12610",
"CVE-2026-6245"
],
"schema_version": "1.7.0",
"summary": "Moderate: sssd security, bug fix, and enhancement update",
"upstream": [
"CVE-2026-12610",
"CVE-2026-6245"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.