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

Red Hat Security Advisory: redhat-ds:11 security update

Affects Red Hat redhat-ds:11Source GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2026-11770· High 7.5

Not known to be exploited · CVSS 7.5 High · fixed in Red Hat Directory Server 11.5 E4S for RHEL 8 package updates : patch Red Hat redhat-ds:11 soon.

Data as of 5 Nov 2026, 17:50 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

Patch: Available – fixed in 11.9

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

A security update for Red Hat Directory Server 11.9 for RHEL 8 is available and should be applied promptly. The update fixes the identified vulnerabilities and is detailed in Red Hat advisory RHSA-2026:55532. Users should follow the instructions in the Red Hat article https://access.redhat.com/articles/11258 to apply the update. No additional mitigation steps are indicated beyond applying the official patch.

Description

Red Hat Directory Server 11.9 for RHEL 8 has received an important security update addressing multiple vulnerabilities including LDAP filter injection, NULL pointer dereference, and a pre-authentication stack buffer overflow. These issues affect the 389-ds-base component and could potentially allow unauthorized access or denial of service. The update fixes CVE-2026-11770, CVE-2026-11788, and CVE-2026-15722. Users are advised to apply the update as detailed in the Red Hat advisory.

Impact

The vulnerabilities fixed in this update include pre-authentication LDAP filter injection, which could allow attackers to manipulate LDAP queries before authentication; a NULL pointer dereference that could cause denial of service; and a stack buffer overflow that could lead to memory corruption or potential code execution. The overall impact is rated as Important by Red Hat, indicating significant security concerns that could affect the confidentiality, integrity, or availability of the Directory Server.

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, 17:50 UTC

WeaknessesCWE-90, CWE-476, CWE-121

Technical details

References

Community reviews

Related threats