CVE-2026-11770VulnerabilityPublished 17 Aug 2026Updated 5 Nov 2026

Red Hat Security Advisory: 389-ds-base security update

Affects Red Hat 389-ds-baseSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-11770· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 5 Nov 2026, 18:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (redhat)	CVSS 3.1	7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 31 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hat Directory Server 11.5 E4S for RHEL 8redhat-ds:11	Affected–	Fixed in–
Red Hat Directory Server 11.7 E4S for RHEL 8redhat-ds:11	Affected–	Fixed in–
Red Hat Directory Server 11.9 for RHEL 8redhat-ds:11	Affected–	Fixed in–
Red Hat Directory Server 12.2 E4S for RHEL 9redhat-ds:12	Affected–	Fixed in–
Red Hat Directory Server 12.4 E4S for RHEL 9redhat-ds:12	Affected–	Fixed in–
Red Hat Enterprise Linux 10389-ds-base	Affected–	Fixed in–

AI-suggested

Red Hat has released updated 389-ds-base packages for Red Hat Enterprise Linux 9.4 and related variants that address these vulnerabilities. Users should apply the security update as detailed in Red Hat advisory RHSA-2026:55422. For update instructions, refer to https://access.redhat.com/articles/11258. Applying these official patches is the recommended and effective mitigation.

Description

Multiple security vulnerabilities have been identified and fixed in the 389 Directory Server (389-ds-base) package used in Red Hat Enterprise Linux 9.4. These include a pre-authentication LDAP filter injection, a NULL pointer dereference in the BER parser, and a pre-authentication stack buffer overflow via unbounded replica ID parsing. These issues could potentially allow attackers to cause denial of service or execute arbitrary code. Red Hat has released updates addressing these vulnerabilities.

Impact

The vulnerabilities allow pre-authentication attacks that could lead to LDAP filter injection, denial of service via NULL pointer dereference, and potential arbitrary code execution through a stack buffer overflow. These flaws affect the core LDAP server functionality, potentially impacting the security and stability of directory services relying on 389-ds-base. No known exploits in the wild have been reported at this time.

Summary

The 389 Directory Server, an LDAPv3 compliant server included in Red Hat Enterprise Linux 9.4, was found to have three security vulnerabilities: CVE-2026-11770, a pre-authentication LDAP filter injection in the CleanAllRUV status check; CVE-2026-11788, a NULL pointer dereference in the deref control plugin BER parser; and CVE-2026-15722, a pre-authentication stack buffer overflow in get_ruvelement_from_berval() due to unbounded replica ID parsing. Red Hat issued an important security advisory (RHSA-2026:55422) providing updated packages that fix these issues. The advisory covers multiple architectures including x86_64, ppc64le, aarch64, and s390x for Red Hat Enterprise Linux 9.4 variants.

CWE-90Improper Neutralization of Special Elements used in an LDAP Query (LDAP Injection) (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
LDAP Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.7 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
The product writes past the end of a buffer that was allocated on the stack.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2026, 18:02 UTC

WeaknessesCWE-90, CWE-476, CWE-121

Technical details

References

Community reviews

Related threats