A flaw was found in sssd-kcm. A local user or process able to connect to the sssd-kcm UNIX socket can exploit this vulnerability. By sending a large request length header and then stalling the connection, an attacker can cause the system to preallocate significant memory. This leads to memory exhaustion within the sssd-kcm responder, resulting in a Denial of Service (DoS) for affected deployments.
CVE-2026-80048
MEDIUMPre-NVD 5.55.5Trending — 5 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.5 from GitHub Security Advisory published 2026-10-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
5.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: No code on recordExposed services: Not assessed
No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.
- CVSS v3
- 5.5
- EG Score
- 5.5MEDIUMhigh confidence
- EG Risk
- 41EG Risk 41/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity55% × 45%The EG Score, 5.5 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (2)
Auto-updated Oct 7, 2026No fix on record yet. Sources: redhat.
Red Hat
2479377 – (CVE-2026-80048) CVE-2026-80048 sssd: sssd-kcm: Local Denial of Service via excessive memory preallocation
https://bugzilla.redhat.com/show_bug.cgi?id=2479377Red HatMentions a patch (unverified)
CVE-2026-80048 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-80048Vendor Advisories for CVE-2026-80048(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| sssd | 2.10.1-1 ... 2.9.5-5 (26 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| sssd | 2.10.1-2 ... 2.13.1-3 (11 versions) |
| — |
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 time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-11 19:21 UTCEG score recompute
- 2026-10-11 17:56 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64 · GitHub CVSS 5.5
- 2026-10-11 16:37 UTCEG score recompute
- 2026-10-11 13:56 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-10 18:18 UTCEG score recompute
- 2026-10-10 18:18 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64 · GitHub CVSS 5.5
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-09 18:57 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64 · GitHub CVSS 5.5
- 2026-10-08 19:41 UTCEG score recompute
- 2026-10-08 19:41 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64 · GitHub CVSS 5.5
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
- 2026-10-07 20:24 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64
- 2026-10-07 19:43 UTCEG score recomputeFirst assessed: 5.5 MEDIUM
- 2026-10-07 19:42 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64
- 2026-10-07 19:41 UTCMITRE cvelistV5CVSS v3 → 5.5 · severity → MEDIUM
- 2026-10-07 14:49 UTCGHSA enrichmentGHSA-m2fx-2vhw-gg64
- 2026-10-07 00:20 UTCNVD update
- 2026-10-06 23:36 UTCEG score recompute
- 2026-10-06 23:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-80048?
CVE-2026-80048 is a medium-severity vulnerability; its CVE record was published on October 6, 2026. A flaw was found in sssd-kcm. A local user or process able to connect to the sssd-kcm UNIX socket can exploit this vulnerability. By sending a large request length header and then stalling the connection, an attacker can cause the system to preallocate significant memory. This leads to memory…
When was CVE-2026-80048 made public?
CVE-2026-80048 was made public on October 6, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2026. EchelonGraph's copy of the record carries a last-modified date of October 7, 2026; the record at its source may have been updated since.
Is CVE-2026-80048 actively exploited?
CVE-2026-80048 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-80048?
CVE-2026-80048 has a CVSS v3.1 base score of 5.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-80048?
No fix for CVE-2026-80048 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-80048 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-80048
Is Your Infrastructure Affected by CVE-2026-80048?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.