Cyber Resilience

CVE-2026-11770

Redhat Enterprise Linux 10.0 … 9.0

Published
31 July 2026
Modified
07 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0048 39th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2026-11770 is a high-severity LDAP Injection (CWE-90) vulnerability in Redhat Enterprise Linux. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

boolean match result, the attacker can extract sensitive server configuration metadata, including replication bind DNs and password storage scheme information.

CWE(s)
CWE-90

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-6237Same product: Redhat 389 Directory Server
CVE-2026-14940Same product: Redhat 389 Directory Server
CVE-2026-11785Same product: Redhat 389 Directory Server
CVE-2026-15722Same product: Redhat 389 Directory Server
CVE-2026-11789Same product: Redhat 389 Directory Server
CVE-2026-11791Same product: Redhat 389 Directory Server
CVE-2026-11786Same product: Redhat 389 Directory Server
CVE-2026-12528Same product: Redhat 389 Directory Server
CVE-2026-15041Same product: Redhat 389 Directory Server
CVE-2026-9064Same product: Redhat 389 Directory Server

Affected Assets

redhat
directory server
11.0, 12.0, 13.0
redhat
389 directory server
all versions
redhat
enterprise linux
10.0, 7.0, 8.0, 9.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.6

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

A.8.27 Secure system architecture and engineering principles none match
mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

A.8.3 Information access restriction none match
none

Information access restriction limits who can query LDAP but does not address how queries are built.

References