Medium [CVE-2026-14940] heap-buffer-overflow in DN normalization via quoted multivalued RDN
This medium-severity Red Hat Linux advisory covers CVE-2026-14940 affecting Red Hat Directory Server 11, Red Hat Directory Server 12, Red Hat Directory Server 13.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
A heap-buffer-overflow flaw was found in 389 Directory Server (389-ds-base). When normalizing a Distinguished Name (DN) that contains a legacy-quoted value encoding a multivalued nested Relative Distinguished Name (RDN), the server can write past the end of a heap allocation while sorting RDN attribute-value pairs.
An unauthenticated remote attacker can trigger this condition by sending an LDAP operation whose DN reaches the DN normalization routine, such as a search with a crafted base DN. This can corrupt heap memory and may cause denial of service.
Red Hat rates this issue as Moderate impact. In 389-ds-base, DN normalization of a crafted legacy-quoted multivalued RDN can corrupt heap memory during internal attribute-value sorting.
Any unauthenticated client that can reach the LDAP service and supply a malformed DN in an operation such as search, bind, add, or modify can trigger the bug.
In standard production builds, the server often rejects the malformed DN with "Invalid DN syntax" and continues operating; the heap corruption may be silent rather than immediately terminating ns-slapd.
Denial of service is more reliably observed when heap debugging is enabled (for example AddressSanitizer or MALLOC_CHECK_=3), or depending on heap layout and subsequent memory allocator activity. There is no configuration switch to disable DN normalization for client-supplied DNs.
Is CVE-2026-14940 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-14940 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-14940?
The advisory VulniPulse tracks names no fixed release. Follow Red Hat's guidance for workarounds and updates.
Confirm against the vendor advisory before you patch.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists. Confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Official advisory · high-confidence parse· fetched 13 days ago·verify at source
Get an email when Red Hat RHEL & SELinux publishes the next one.
See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
- CVE-2026-64849Aug 17, 2026Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.