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
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 3.7Exploit: None knownExposed services: Not assessed

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

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.7LOWmedium confidence
EG Risk
17
EG Risk 17/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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 rangeFix by version rangeDependents
389-ds-base1.4.4.11-2 ... 3.1.2+vendor1-2 (23 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base2.3.1+dfsg1-1 ... 3.3.1-3 (18 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
389-ds-base3.1.2+dfsg1-1 ... 3.3.1-3 (8 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-10-09 20:06 UTCEPSS rescore
  2. 2026-10-08 17:11 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:42 UTCEPSS rescore
  6. 2026-10-04 23:21 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 16:20 UTCEG score recompute
  10. 2026-10-01 16:20 UTCGHSA enrichment
  11. 2026-09-30 15:02 UTCEPSS rescore
  12. 2026-09-29 15:20 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-28 13:26 UTCEG score recompute
  15. 2026-09-28 13:26 UTCGHSA enrichment
  16. 2026-09-27 13:47 UTCEPSS rescore
  17. 2026-09-26 15:58 UTCEPSS rescore
  18. 2026-09-23 06:13 UTCEG score recompute
  19. 2026-09-23 06:13 UTCGHSA enrichment
  20. 2026-09-18 19:27 UTCEPSS rescore
  21. 2026-09-18 05:46 UTCEG score recompute
  22. 2026-09-18 05:46 UTCGHSA enrichment
  23. 2026-09-16 14:07 UTCEPSS rescore
  24. 2026-09-16 05:14 UTCEPSS rescore
  25. 2026-09-13 16:46 UTCEPSS rescore
Show 75 more
  1. 2026-09-12 15:00 UTCEPSS rescore
  2. 2026-09-12 03:39 UTCEG score recompute
  3. 2026-09-12 03:39 UTCGHSA enrichment
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 22:50 UTCEG score recompute
  11. 2026-09-05 22:50 UTCGHSA enrichment
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 14:11 UTCEPSS rescore
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 07:38 UTCEG score recompute
  18. 2026-08-30 07:38 UTCGHSA enrichment
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-25 13:31 UTCEG score recompute
  25. 2026-08-25 13:31 UTCGHSA enrichment
  26. 2026-08-23 00:19 UTCEPSS rescore
  27. 2026-08-22 13:34 UTCEG score recompute
  28. 2026-08-22 13:34 UTCGHSA enrichment
  29. 2026-08-21 23:49 UTCEPSS rescore
  30. 2026-08-20 22:55 UTCEPSS rescore
  31. 2026-08-19 17:03 UTCEPSS rescore
  32. 2026-08-19 13:29 UTCEG score recompute
  33. 2026-08-19 13:29 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 13:32 UTCEG score recompute
  38. 2026-08-16 13:32 UTCGHSA enrichment
  39. 2026-08-16 02:14 UTCEPSS rescore
  40. 2026-08-15 01:30 UTCEPSS rescore
  41. 2026-08-13 22:00 UTCEPSS rescore
  42. 2026-08-13 13:34 UTCEG score recompute
  43. 2026-08-13 13:34 UTCGHSA enrichment
  44. 2026-08-12 13:50 UTCEPSS rescore
  45. 2026-08-11 13:42 UTCEPSS rescore
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-10 13:38 UTCEG score recompute
  48. 2026-08-10 13:38 UTCGHSA enrichment
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-07 13:41 UTCEG score recompute
  52. 2026-08-07 13:41 UTCGHSA enrichment
  53. 2026-08-06 13:46 UTCEPSS rescore
  54. 2026-08-05 19:17 UTCEPSS rescore
  55. 2026-08-04 15:09 UTCEPSS rescore
  56. 2026-08-04 13:43 UTCEG score recompute
  57. 2026-08-04 13:43 UTCGHSA enrichment
  58. 2026-08-04 10:38 UTCEPSS rescore
  59. 2026-08-03 10:35 UTCEPSS rescore
  60. 2026-08-02 02:26 UTCEPSS rescore
  61. 2026-08-01 12:23 UTCEG score recompute
  62. 2026-08-01 12:23 UTCGHSA enrichment
  63. 2026-08-01 04:15 UTCEPSS rescore
  64. 2026-07-30 16:27 UTCEPSS rescore
  65. 2026-07-30 01:30 UTCEPSS rescore
  66. 2026-07-29 12:26 UTCEG score recompute
  67. 2026-07-29 12:26 UTCGHSA enrichment
  68. 2026-07-28 15:36 UTCEPSS rescore
  69. 2026-07-27 14:13 UTCEPSS rescore
  70. 2026-07-26 14:54 UTCEPSS rescore
  71. 2026-07-26 14:54 UTCEPSS rescore
  72. 2026-07-26 12:29 UTCEG score recompute
  73. 2026-07-26 12:29 UTCGHSA enrichment
  74. 2026-07-25 14:17 UTCEPSS rescore
  75. 2026-07-24 14:17 UTCEPSS rescore

Related CVEs(same product + same CWE)

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 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.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15041?
CVE-2026-15041 has a CVSS base score of 3.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15041?
No fix for CVE-2026-15041 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-15041 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs