# CVE-2026-78701: 389-ds-base: 389-ds-base: cve-2026-11610 incomplete fix may introduce a connection-stall dos

> A remote authenticated attacker can cause a connection stall and resource exhaustion in 389-ds-base via a crafted SASL UNBIND request, leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** AZL-98045, GHSA-xmh3-2gr9-2rwp, UBUNTU-CVE-2026-78701

## What is CVE-2026-78701?

CVE-2026-78701 is a medium-severity denial of service vulnerability in Red Hat Directory Server 11, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in 389-ds-base. A remote, authenticated attacker could exploit a vulnerability in the Simple Authentication and Security Layer (SASL) UNBIND process. By sending a specially crafted request, the attacker can cause a connection to stall, leading to resource exhaustion and a Denial of Service (DoS) for the server.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

Apply the vendor's patch.

## Is CVE-2026-78701 being exploited?

There is no known exploitation of CVE-2026-78701 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78701 is a medium-severity denial of service vulnerability in Red Hat Directory Server 11, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78701 in the wild and no public exploit code.

Affected product: Red Hat Directory Server 11. 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-78701/ (Markdown: https://insights.sbomify.com/CVE-2026-78701/index.md)
```

## Sources

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

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