CVE-2026-12610

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

Score 6.4 from GitHub Security Advisory published 2026-06-30. a secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.4
EG Score
6.4(high)
EPSS
5.0%
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Advisory Details (3)

Auto-updated Jun 30, 2026
Patch available. Sources: redhat.
generic

Use-after-free crash in PAM responder during YubiKey / PKCS#11 authentication · Issue #8796 · SSSD/sssd · GitHub

https://github.com/SSSD/sssd/issues/8796
redhat

2490288 – (CVE-2026-12610) CVE-2026-12610 sssd: Use-after-free crash in SSSD' 'sssd_pam' process

https://bugzilla.redhat.com/show_bug.cgi?id=2490288
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-12610

Vendor Advisories for CVE-2026-12610(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 17:07 UTCEG score recompute
  2. 2026-07-06 17:07 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 16:00 UTCEG score recompute
  6. 2026-07-05 16:00 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 14:54 UTCEG score recompute
  10. 2026-07-04 14:54 UTCGHSA enrichment
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-03 13:48 UTCEG score recompute
  13. 2026-07-03 13:48 UTCGHSA enrichment
  14. 2026-07-02 12:43 UTCEG score recompute
  15. 2026-07-02 12:43 UTCGHSA enrichment
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-07-01 11:37 UTCEG score recompute
  19. 2026-07-01 11:37 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 10:32 UTCEG score recompute
  22. 2026-06-30 10:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-12610?
CVE-2026-12610 is a medium vulnerability published on June 30, 2026. 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…
When was CVE-2026-12610 disclosed?
CVE-2026-12610 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12610 actively exploited?
CVE-2026-12610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12610?
CVE-2026-12610 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-12610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12610, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-12610

Explore →

Is Your Infrastructure Affected by CVE-2026-12610?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs