Live › vulnerability › CVE-2026-117548
A NULL pointer dereference in 389-ds-base happens when a ModifyDN (rename) request uses a schema alias such as "commonName" instead of the canonical attribute name "cn" as the new RDN. An authenticated user with rename permission on an entry can crash the directory server, causing a denial of service.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 07:23 UTC. All times on this page are UTC.
Teams running 389 Directory Server (389-ds-base) as an LDAP directory are exposed. The attacker must hold the ModifyDN (rename) permission on the affected entry, so deployments where only administrators can rename entries carry lower risk. The sources do not name affected version ranges.
No product ranges from the sources yet.
rpm -q 389-ds-base or dpkg -l 389-ds-base and compare it to the fixed version.No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A NULL pointer dereference flaw was found in 389-ds-base. This flaw occurs when a ModifyDN (rename) operation uses an attribute's schema alias name (such as "commonName") instead of its canonical name (such as "cn") as the new relative distinguished name. An authenticated attacker with the ModifyDN (rename) permission on the affected entry can use this flaw to crash the directory server, causing a denial of service.
This page as .md · .json · in your agent: get_signal("CVE-2026-117548")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.