CVE-2026-15041 json
389-ds-base: 389-ds-base: non-constant-time comparison in pbkdf2-sha256 password verification
published 2026-07-08 4 mo ago modified 2026-11-06 2 d ago also EUVD-2026-42213
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-15041 updated cvss 3.7
389-ds-base: 389-ds-base: Non-constant-time comparison in PBKDF2-SHA256 password verification
-
Red Hat Directory Server 11 389-ds-base Red Hat Directory Server 12 389-ds-base Red Hat Directory Server 13 389-ds-base Red Hat Enterprise Linux 7 389-ds-base, 389-ds-base-libs, 389-ds-base-snmp Red Hat Enterprise Linux 8 389-ds-base, cockpit-389-ds, python3-lib389, 389-ds-base-libs, 389-ds-base-snmp, 389-ds-base-legacy-tools Red Hat Enterprise Linux 9 389-ds-base, python3-lib389, 389-ds-base-libs, 389-ds-base-snmpaffected: workaround, no fix available “If possible, configure 389 Directory Server to use an alternative password storage scheme (e.g., SSHA512 or GOST-Yescrypt) which uses constant-time comparison.”
+1 more productsfewer
Red Hat Enterprise Linux 10 389-ds-base -
Red Hat Enterprise Linux 6 389-ds-base, 389-ds-base-libsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Red Hat Red Hat Directory Server 11
- Red Hat Red Hat Directory Server 12
- Red Hat Red Hat Directory Server 13
- Red Hat Red Hat Enterprise Linux 10
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Enterprise Linux 7
- Red Hat Red Hat Enterprise Linux 8
- Red Hat Red Hat Enterprise Linux 9
Classification
- Weakness
-
- CWE-208 Observable Timing Discrepancy
References
-
access.redhat.com
/security/cve/CVE-2026-15041
vdb-entry, vendor-advisory
-
bugzilla.redhat.com
/show_bug.cgi?id=2498022
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2026-15041
- NVD CVE-2026-15041
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.