CVE-2026-19404: 389-ds-base: 389-ds-base: missing authorization allows anonymous clients to start or abort cleanallruv replication maintenance
A flaw was found in 389 Directory Server. The CleanAllRUV and Abort CleanAllRUV replication-maintenance extended operations perform no authorization check, allowing an unauthenticated remote attacker to invoke them when nsslapd-allow-anonymous-access is enabled (the default), or any authenticated low-privilege user to invoke them otherwise. This allows removal of a replica ID from replication metadata, purging of changelog records, and interruption of administrator-initiated cleanup, which can leave replication inconsistent or unavailable.
Other sources
A flaw was found in 389 Directory Server. The LDAP extended-operation handlers that start (multisupplierextopcleanruv) and abort (multisupplierextopabortcleanruv) the CleanAllRUV replication-maintenance task in ldap/servers/plugins/replication/replextop.c perform no check on the connection's bind DN or authentication state, unlike the analogous multisupplierextopStartNSDS50ReplicationRequest handler in the same file, which explicitly verifies the connection is an authorized replication updatedn via replicaisupdatedn(). Under the default nsslapd-allow-anonymous-access configuration, a fully anonymous network client that can reach a supplier's LDAP listener and knows the target suffix and replica ID can start or abort CleanAllRUV; if anonymous access has been restricted, any client that has completed a successful bind (regardless of privilege level) can do the same, since the handlers themselves perform no further authorization check. This lets the client cause unauthorized removal of a replica ID from replication metadata, purge related changelog records, and interrupt administrator-initiated cleanup operations, potentially leaving replication inconsistent or unavailable. Reported by Andrew Rukin (Arenadata), who verified the issue against 389-ds-base-3.3.0-5.fc45.x8664 with both a single supplier and two replicating suppliers, and confirmed the abort handler likewise lacks the check by source review. Independently reproduced live in an isolated sandbox against the same NVR: the anonymous start request was accepted and genuinely executed (RUV entry removed, changelog purged), a well-formed request to the sibling, protected StartNSDS50ReplicationRequest handler was correctly rejected under the same unauthenticated precondition, and cross-supplier propagation was confirmed (a second supplier independently completed the identical cleanup via its replication agreement with the targeted supplier, without ever receiving a direct request from the client).
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Disable or restrict nsslapd-allow-anonymous-access so unauthenticated remote clients cannot invoke CleanAllRUV (multisupplier_extop_cleanruv) or Abort CleanAllRUV (multisupplier_extop_abort_cleanruv).
389 Directory Server (nsslapd) nsslapd-allow-anonymous-access = disabled / restricted - Compensating control
Ensure only authorized/required clients can reach the supplier LDAP listener (network-level restriction such as firewall/ACL/WAF) to reduce the ability of anonymous or low-privilege bound clients to invoke the affected extended operations.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-19404?
CVE-2026-19404 has a medium severity rating of 6.5.
What does CVE-2026-19404 allow attackers to do?
CVE-2026-19404 allows unauthenticated remote attackers to start or abort CleanAllRUV replication maintenance operations.
How can I mitigate CVE-2026-19404?
To mitigate CVE-2026-19404, disable anonymous access by adjusting the nsslapd-allow-anonymous-access configuration.
Is CVE-2026-19404 present in all versions of 389 Directory Server?
CVE-2026-19404 affects the 389-ds-base version of the 389 Directory Server where anonymous access is enabled.
How does CVE-2026-19404 impact data integrity?
CVE-2026-19404 has a low impact on confidentiality, a medium impact on integrity, and a high impact on availability.