CVE Tools
Track your stack

CVE-2026-76560

389-ds-base: 389-ds: anonymous ldap client can defeat selfdn aci bind-rule checks via empty bind dn

No known exploitation. EPSS puts it in the 46th percentile. Fixed versions are out.

CVSS 3.17.5HighEPSS percentile46th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products5 fixed builds listed below

Published Updated Sources: CVE.org, NVD

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Red Hat Directory Server 11.5 E4S for RHEL 8Fixed builds8060020260908152739.0ca98e7eStated by: CVE record
  • Red Hat Directory Server 11.7 E4S for RHEL 8Fixed builds8080020260903102346.f969626eStated by: CVE record
  • Red Hat Directory Server 11.9 for RHEL 8Fixed builds8100020260904171440.37ed7c03Stated by: CVE record
  • Red Hat Directory Server 12.2 E4S for RHEL 9Fixed builds9020020260903155914.1674d574Stated by: CVE record
  • Red Hat Directory Server 12.4 E4S for RHEL 9Fixed builds9040020260903102623.1674d574Stated by: CVE record

Versions as the sources state them. 13 more products have version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

A flaw was found in 389 Directory Server. The SELFDN ACI bind-rule evaluator incorrectly matches an anonymous LDAP client's empty bind DN against an empty stored attribute value, allowing an unauthenticated client to satisfy access control checks intended to require a matching authenticated identity. This can allow an anonymous LDAP client to perform an operation, such as adding or modifying a directory entry, that a SELFDN-based ACI intended to restrict to a specific authenticated user.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS46th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 46th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

20 events over 31 days, from the signal feeds we watch.

  1. Workaround availablerecord updated
  2. OpenVAS check added
  3. Workaround availableworkaround available, workaround available, workaround available, workaround available, workaround available, record updated, record updated, record updated, record updated, record updated, record updated
  4. Workaround availablepublished, weakness classified, att&ck mapped, record updated

Affected products

And 16 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

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

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality NoneNo confidentiality impact
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 16 more references. See all after sign-in

In the news

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Red Hat, not every advisory.