# CVE-2026-104037: Sssd: sssd: denial of service via packet length underflow in autofs responder

> A local attacker can cause a denial of service in the SSSD autofs responder by sending a crafted request that triggers an integer underflow and memory crash.

- **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:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-104037, GHSA-c66h-w9px-9v6r, UBUNTU-CVE-2026-104037

## What is CVE-2026-104037?

CVE-2026-104037 is a medium-severity 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. A local attacker can exploit this issue by sending a specially crafted request with an invalid packet length to the autofs responder UNIX socket. This causes an integer underflow and an out-of-bounds memory read, which can crash the responder process and result in a denial of service (DoS).

Weakness: CWE-125 (Out-of-bounds Read)

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


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

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

## Is CVE-2026-104037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104037 is a medium-severity 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-104037 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-104037/ (Markdown: https://insights.sbomify.com/CVE-2026-104037/index.md)
```

## Sources

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

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