Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2026-11770

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')

Published: Jul 31, 2026 | Modified: Aug 18, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-11770
CWEhttps://cwe.mitre.org/data/definitions/90.html

A flaw was found in 389 Directory Server. An unauthenticated remote attacker can inject LDAP search filters into the CleanAllRUV replication status-check extended operation. Because the handler performs the search against cn=config with elevated replication plugin privileges and returns a boolean match result, the attacker can extract sensitive server configuration metadata, including replication bind DNs and password storage scheme information.

Weakness

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.

Affected Software

NameVendorStart VersionEnd Version
Directory_serverRedhat11.0 (including)11.0 (including)
Directory_serverRedhat12.0 (including)12.0 (including)
Directory_serverRedhat13.0 (including)13.0 (including)
389_directory_serverRedhat- (including)- (including)
Enterprise_linuxRedhat7.0 (including)7.0 (including)
Enterprise_linuxRedhat8.0 (including)8.0 (including)
Enterprise_linuxRedhat9.0 (including)9.0 (including)
Enterprise_linuxRedhat10.0 (including)10.0 (including)
Red Hat Directory Server 11.7 E4S for RHEL 8RedHatredhat-ds:11-8080020260806114250.f969626e*
Red Hat Directory Server 11.9 for RHEL 8RedHatredhat-ds:11-8100020260803140625.37ed7c03*
Red Hat Directory Server 12.2 E4S for RHEL 9RedHatredhat-ds:12-9020020260730155601.1674d574*
Red Hat Directory Server 12.4 E4S for RHEL 9RedHatredhat-ds:12-9040020260810131422.1674d574*
Red Hat Enterprise Linux 10RedHat389-ds-base-0:3.2.0-9.el10_2*
Red Hat Enterprise Linux 10.0 Extended Update SupportRedHat389-ds-base-0:3.0.6-20.el10_0*
Red Hat Enterprise Linux 7 Extended Lifecycle SupportRedHat389-ds-base-0:1.3.11.1-14.el7_9*
Red Hat Enterprise Linux 8RedHat389-ds:1.4-8100020260806150504.25e700aa*
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportRedHat389-ds:1.4-8040020260803141511.96015a92*
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnRedHat389-ds:1.4-8040020260803141511.96015a92*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportRedHat389-ds:1.4-8060020260806120442.824efc52*
Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-OnRedHat389-ds:1.4-8060020260806120442.824efc52*
Red Hat Enterprise Linux 8.8 Telecommunications Update ServiceRedHat389-ds:1.4-8080020260806114228.6dbb3803*
Red Hat Enterprise Linux 8.8 Update Services for SAP SolutionsRedHat389-ds:1.4-8080020260806114228.6dbb3803*
Red Hat Enterprise Linux 9RedHat389-ds-base-0:2.8.0-9.el9_8*
Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsRedHat389-ds-base-0:2.2.4-20.el9_2*
Red Hat Enterprise Linux 9.4 Update Services for SAP SolutionsRedHat389-ds-base-0:2.4.5-27.el9_4*
Red Hat Enterprise Linux 9.6 Extended Update SupportRedHat389-ds-base-0:2.6.1-23.el9_6*

Potential Mitigations

  • 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.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use