CVE-2026-15041: 389-ds-base: 389-ds-base: non-constant-time comparison in pbkdf2-sha256 password verification

Published Jul 8, 2026
·
Updated

A flaw was found in 389 Directory Server. The PBKDF2-SHA256 password verification function pbkdf2sha256pwcmp() in ldap/servers/plugins/pwdstorage/pbkdf2pwd.c uses standard memcmp() for hash comparison instead of the project's constant-time slapictmemcmp(). Every other password storage scheme in the same plugin uses slapictmemcmp(), which was introduced specifically to prevent timing side-channels (see CVE-2016-5405). This inconsistency allows a remote attacker with network access to the LDAP service to potentially infer partial hash information through repeated timing measurements of LDAP bind attempts. Practical exploitation is extremely difficult due to the PBKDF2 work factor (8192+ iterations, ~2ms computation time) which dominates and masks the nanosecond-level memcmp timing delta.

Other sources

A flaw was found in 389 Directory Server. The PBKDF2-SHA256 password verification function uses standard memcmp() for comparing password hashes instead of a constant-time comparison function. A remote attacker could potentially use timing measurements of LDAP bind attempts to infer partial hash information, though practical exploitation is extremely difficult due to PBKDF2 computational overhead.

MITRE

Affected Software

9 affected components
Red Hat 389 Directory Server
redhat Directory Server=11.0
redhat Directory Server=12.0
redhat Directory Server=13.0
redhat 389 Directory Server
redhat Enterprise Linux=7.0
redhat Enterprise Linux=8.0
redhat Enterprise Linux=9.0
redhat Enterprise Linux=10.0

Event History

Jul 8, 2026
Data Sourced
via Red Hat·10:02 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·10:15 AM
Data Sourced
via MITRE·10:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-15041?

The severity level of CVE-2026-15041 is classified as low, with a score of 3.7.

2

How do I fix CVE-2026-15041?

To fix CVE-2026-15041, you should update to the patched version of Red Hat 389 Directory Server that addresses this vulnerability.

3

What impact does CVE-2026-15041 have on password security?

CVE-2026-15041 introduces a risk of timing attacks during password verification, potentially compromising user passwords.

4

Which product is affected by CVE-2026-15041?

The affected product is the Red Hat 389 Directory Server.

5

Is CVE-2026-15041 exploitable remotely?

Yes, CVE-2026-15041 is exploitable remotely, as indicated by its attack vector classification.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203