CVE-2026-6245 | Sssd: out-of-bounds read in the sssd

A flaw was found in the System Security Services Daemon (SSSD). The pam_passkey_child_read_data() function within the PAM passkey responder fails to properly handle raw bytes received from a pipe. Because the data is treated as a NUL-terminated C string without explicit termination, it results in an out-of-bounds read when processed by functions like snprintf(). A local attacker could potentially trigger this vulnerability by initiating a crafted passkey authentication request, causing the SSSD PAM responder to crash, resulting in a local Denial of Service (DoS).

Published: 2026-04-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-6245 is rated Low Risk (23.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.14%). 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-6245

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-15 0.01% 0.14% +0.13%
2 2026-04-16 — 0.01% —

Full EPSS history (2 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2026-6245

OS Trackers for CVE-2026-6245

vendor priority summary link
debian unimportant CVE-2026-6245 unimportant priority: Debian including 1 source packages (sssd), 4 status rows across 4 suites (bookworm, bullseye, sid, trixie): open 2, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-6245
redhat medium — https://access.redhat.com/security/cve/CVE-2026-6245
suse medium CVE-2026-6245 severity moderate: SUSE including 28 source package names (libipa_hbac-devel, libipa_hbac0, …), 299 product×package rows across 19 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (19 product lines)): Known Not Affected 299. https://www.suse.com/security/cve/CVE-2026-6245/
ubuntu medium CVE-2026-6245 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-6245

Affected software / configurations for CVE-2026-6245

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-6245

cvelogic Threat Intelligence