# CVE-2026-19843: 389-ds-base: 389-ds-base: command injection via unescaped ldap dn in cockpit 389 console ldap editor

> An attacker with delegated privileges can inject shell commands via a malicious LDAP DN, leading to root code execution when an admin views the entry in the Cockpit console.

- **Severity:** High 8.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Sep 2026
- **Updated:** 8 Oct 2026
- **Also known as:** AZL-99986, DEBIAN-CVE-2026-19843, GHSA-p34m-7cj2-q64p, RHSA-2026:64768, RHSA-2026:64769, RHSA-2026:64782, RHSA-2026:65375, UBUNTU-CVE-2026-19843

## What is CVE-2026-19843?

CVE-2026-19843 is a high-severity command injection vulnerability in Red Hat Directory Server 11, published on 7 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A flaw was found in 389-ds-base. The Cockpit 389 Console's LDAP editor constructs an ldapsearch command by embedding an LDAP entry's distinguished name (DN) into a shell command string without proper escaping. An LDAP user with delegated privileges to create or rename directory entries could craft a malicious DN containing shell metacharacters. When a Cockpit administrator subsequently views the entry in the 389 Console, the embedded shell command executes with root privileges on the directory server host.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `389-ds-base` | Red Hat:directory_server:12.8::el9 | All versions | 0:2.8.0-7.module+el9dsrv+24844+8988a132 |
| `cockpit-389-ds` | Red Hat:directory_server:12.8::el9 | All versions | 0:2.8.0-7.module+el9dsrv+24844+8988a132 |
| `389-ds-base` | Red Hat:directory_server:13.2::el10 | All versions | 0:3.2.0-7.el10dsrv |
| `cockpit-389-ds` | Red Hat:directory_server:13.2::el10 | All versions | 0:3.2.0-7.el10dsrv |
| `389-ds-base` | Red Hat:directory_server_e2s:13.0::el10 | All versions | 0:3.0.6-4.el10dsrv |
| `cockpit-389-ds` | Red Hat:directory_server_e2s:13.0::el10 | All versions | 0:3.0.6-4.el10dsrv |
| `389-ds-base` | Red Hat:directory_server_eus:12.6::el9 | All versions | 0:2.6.1-4.module+el9dsrv+24810+65883465 |
| `cockpit-389-ds` | Red Hat:directory_server_eus:12.6::el9 | All versions | 0:2.6.1-4.module+el9dsrv+24810+65883465 |

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

Apply the vendor's patch.

## Is CVE-2026-19843 being exploited?

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

Public exploit code:

- Patch: Privilege escalation via web UI (Cisco IOS XE) (github_poc): https://github.com/gduma-phData/patch-CVE-2026-19843

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19843 is a high-severity command injection vulnerability in Red Hat Directory Server 11, published on 7 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19843 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-19843/ (Markdown: https://insights.sbomify.com/CVE-2026-19843/index.md)
```

## Sources

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

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