CVE-2026-18651

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-08-03. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: 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. During SASL PLAIN authentication, the server installs connection-level bind credentials before performing the account-lock check. If the account is subsequently found to be locked, the bind is reported as failed to the client, but the already-installed authenticated state on the connection is not reverted. A client that supplies valid credentials for an account that has been administratively locked can continue to use the same connection with that account's privileges, defeating account lock as an access-revocation control.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 9, 2026

Advisory Details (2)

Auto-updated Aug 3, 2026
Patch available. Sources: redhat.
redhat

2510617 – (CVE-2026-18651) CVE-2026-18651 389-ds-base: 389-ds-base: SASL PLAIN bind installs connection credentials before account-lock check, allowing continued access as a locked account

https://bugzilla.redhat.com/show_bug.cgi?id=2510617
redhat Patch Available

CVE-2026-18651 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-18651

Vendor Advisories for CVE-2026-18651(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 19× in last 7d / 49× 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-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:22 UTCGHSA enrichment
  3. 2026-08-19 19:00 UTCEG score recompute
  4. 2026-08-19 19:00 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 18:21 UTCEG score recompute
  7. 2026-08-18 18:20 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 16:54 UTCEG score recompute
  10. 2026-08-17 16:54 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:33 UTCEG score recompute
  13. 2026-08-16 16:33 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 16:12 UTCEG score recompute
  17. 2026-08-15 16:12 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 15:51 UTCGHSA enrichment
  20. 2026-08-13 15:29 UTCGHSA enrichment
  21. 2026-08-12 15:04 UTCEG score recompute
  22. 2026-08-12 15:04 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 14:42 UTCEG score recompute
  25. 2026-08-11 14:42 UTCGHSA enrichment
Show 24 more
  1. 2026-08-11 13:42 UTCEPSS rescore
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-10 14:21 UTCGHSA enrichment
  4. 2026-08-09 14:00 UTCEG score recompute
  5. 2026-08-09 14:00 UTCGHSA enrichment
  6. 2026-08-09 13:46 UTCEPSS rescore
  7. 2026-08-08 19:29 UTCEG score recompute
  8. 2026-08-08 19:29 UTCGHSA enrichment
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-07 19:08 UTCEG score recompute
  11. 2026-08-07 19:08 UTCGHSA enrichment
  12. 2026-08-06 18:46 UTCEG score recompute
  13. 2026-08-06 18:46 UTCGHSA enrichment
  14. 2026-08-06 13:46 UTCEPSS rescore
  15. 2026-08-05 19:17 UTCEPSS rescore
  16. 2026-08-05 18:25 UTCGHSA enrichment
  17. 2026-08-04 18:03 UTCEG score recompute
  18. 2026-08-04 18:03 UTCGHSA enrichment
  19. 2026-08-04 15:10 UTCEPSS rescore
  20. 2026-08-03 17:40 UTCEG score recompute
  21. 2026-08-03 17:12 UTCEG score recompute
  22. 2026-08-03 16:35 UTCEG score recompute
  23. 2026-08-03 15:28 UTCEG score recompute
  24. 2026-08-03 15:28 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18651?
CVE-2026-18651 is a medium vulnerability published on August 3, 2026. A flaw was found in 389 Directory Server. During SASL PLAIN authentication, the server installs connection-level bind credentials before performing the account-lock check. If the account is subsequently found to be locked, the bind is reported as failed to the client, but the already-installed…
When was CVE-2026-18651 disclosed?
CVE-2026-18651 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 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-18651 actively exploited?
CVE-2026-18651 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 93.6% of all scored CVEs.
What is the CVSS score of CVE-2026-18651?
CVE-2026-18651 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-18651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18651, 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-18651

Explore →

Is Your Infrastructure Affected by CVE-2026-18651?

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

Start Free Scan →Browse All CVEs