CVE-2026-15041

LOWPre-NVD 3.73.7—
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-07-08. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
17(Track)
EG Risk 17/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

References (2)

Vendor Advisories for CVE-2026-15041(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
389-ds-base1.4.4.11-2 ... 3.1.2+vendor1-2 (23 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
389-ds-base2.3.1+dfsg1-1 ... 3.1.2+vendor1-2 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
389-ds-base3.1.2+dfsg1-1, 3.1.2+dfsg1-1+deb13u1, 3.1.2+vendor1-1, 3.1.2+vendor1-2——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-25 13:48 UTCEPSS rescore
  2. 2026-08-25 13:31 UTCEG score recompute
  3. 2026-08-25 13:31 UTCGHSA enrichment
  4. 2026-08-23 00:19 UTCEPSS rescore
  5. 2026-08-22 13:34 UTCEG score recompute
  6. 2026-08-22 13:34 UTCGHSA enrichment
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 13:29 UTCEG score recompute
  11. 2026-08-19 13:29 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 13:32 UTCEG score recompute
  16. 2026-08-16 13:32 UTCGHSA enrichment
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 13:34 UTCEG score recompute
  21. 2026-08-13 13:34 UTCGHSA enrichment
  22. 2026-08-12 13:50 UTCEPSS rescore
  23. 2026-08-11 13:42 UTCEPSS rescore
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 13:38 UTCEG score recompute
Show 48 more
  1. 2026-08-10 13:38 UTCGHSA enrichment
  2. 2026-08-09 13:46 UTCEPSS rescore
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-07 13:41 UTCEG score recompute
  5. 2026-08-07 13:41 UTCGHSA enrichment
  6. 2026-08-06 13:46 UTCEPSS rescore
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-04 15:09 UTCEPSS rescore
  9. 2026-08-04 13:43 UTCEG score recompute
  10. 2026-08-04 13:43 UTCGHSA enrichment
  11. 2026-08-04 10:38 UTCEPSS rescore
  12. 2026-08-03 10:35 UTCEPSS rescore
  13. 2026-08-02 02:26 UTCEPSS rescore
  14. 2026-08-01 12:23 UTCEG score recompute
  15. 2026-08-01 12:23 UTCGHSA enrichment
  16. 2026-08-01 04:15 UTCEPSS rescore
  17. 2026-07-30 16:27 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-29 12:26 UTCEG score recompute
  20. 2026-07-29 12:26 UTCGHSA enrichment
  21. 2026-07-28 15:36 UTCEPSS rescore
  22. 2026-07-27 14:13 UTCEPSS rescore
  23. 2026-07-26 14:54 UTCEPSS rescore
  24. 2026-07-26 14:54 UTCEPSS rescore
  25. 2026-07-26 12:29 UTCEG score recompute
  26. 2026-07-26 12:29 UTCGHSA enrichment
  27. 2026-07-25 14:17 UTCEPSS rescore
  28. 2026-07-24 14:17 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:05 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:24 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:30 UTCEPSS rescore
  35. 2026-07-19 02:28 UTCEPSS rescore
  36. 2026-07-18 10:04 UTCEPSS rescore
  37. 2026-07-16 17:02 UTCEPSS rescore
  38. 2026-07-15 16:57 UTCEPSS rescore
  39. 2026-07-15 02:00 UTCEPSS rescore
  40. 2026-07-14 10:44 UTCGHSA enrichment
  41. 2026-07-13 22:30 UTCEPSS rescore
  42. 2026-07-13 06:12 UTCEPSS rescore
  43. 2026-07-12 05:46 UTCEPSS rescore
  44. 2026-07-11 10:47 UTCGHSA enrichment
  45. 2026-07-11 08:27 UTCEPSS rescore
  46. 2026-07-09 19:10 UTCEPSS rescore
  47. 2026-07-08 10:50 UTCEG score recompute
  48. 2026-07-08 10:50 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15041?
CVE-2026-15041 is a low vulnerability published on July 8, 2026. 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…
When was CVE-2026-15041 disclosed?
CVE-2026-15041 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15041 actively exploited?
CVE-2026-15041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.4% of all scored CVEs.
What is the CVSS score of CVE-2026-15041?
CVE-2026-15041 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-15041?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15041, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15041

Explore →

Is Your Infrastructure Affected by CVE-2026-15041?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs