# CVE-2026-80048: Sssd: sssd-kcm: local denial of service via excessive memory preallocation

> A local attacker can cause a denial of service in sssd-kcm by triggering excessive memory preallocation through a stalled connection.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-80048, GHSA-m2fx-2vhw-gg64, UBUNTU-CVE-2026-80048

## What is CVE-2026-80048?

CVE-2026-80048 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-80048?


## How do I fix CVE-2026-80048?

No fix has been published for CVE-2026-80048 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80048 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80048 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80048 and fix it if it is affected.

What it is: CVE-2026-80048 is a medium-severity denial of service vulnerability in Red Hat Enterprise Linux 10, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80048 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80048/ (Markdown: https://insights.sbomify.com/CVE-2026-80048/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80048
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80048
- OSV: https://osv.dev/vulnerability/CVE-2026-80048

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80048/
Summaries are generated and may contain mistakes; the official description above is the record.