CVE-2020-26214

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 65.9%, top 1% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.1
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS: 66%CVSS: 9.1Exploit: NoneExposed: 0

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

In Alerta before version 8.1.0, users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider. Only deployments where LDAP servers are configured to allow unauthenticated authentication mechanism for anonymous authorization are affected. A fix has been implemented in version 8.1.0 that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. As a workaround LDAP administrators can disallow unauthenticated bind requests by clients.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Track*)
EG Risk 72/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
Severity91% × 45%
Exploitation66% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
99.2%
KEV
Not listed

Published

November 6, 2020

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jul 19, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

LDAP authentication bypass with empty password · Advisory · alerta/alerta · GitHub

https://github.com/alerta/alerta/security/advisories/GHSA-5hmm-x8q8-w5jh
github_pr Patch Available

Do not allow LDAP login with empty password

Patch available: alerta/alerta v8.1.0 (PR #1345 merged 2020-10-24)

https://github.com/alerta/alerta/pull/1345
generic

Disallow LDAP anonymous bind · Issue #1277 · alerta/alerta · GitHub

https://github.com/alerta/alerta/issues/1277
github_commit Patch Available

commit 2bfa31779a4c (alerta/alerta)

Patch available: alerta/alerta v8.1.0 (contains commit 2bfa31779a4c)

https://github.com/alerta/alerta/commit/2bfa31779a4c9df2fa68fa4d0c5c909698c5ef65
generic

RFC 4513 - Lightweight Directory Access Protocol (LDAP): Authentication Methods and Security Mechanisms

https://tools.ietf.org/html/rfc4513#section-5.1.2
generic

alerta-server · PyPI

https://pypi.org/project/alerta-server/8.1.0/

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
alerta-server3.1.2 ... 8.0.3 (230 versions)8.1.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 32× 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-07-23 14:15 UTCEPSS rescore
  2. 2026-07-23 14:15 UTCEPSS rescore
  3. 2026-07-23 01:51 UTCEG score recompute
  4. 2026-07-22 22:37 UTCEG score recompute
  5. 2026-07-22 14:05 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-20 17:04 UTCEPSS rescore
  9. 2026-07-20 17:04 UTCEPSS rescore
  10. 2026-07-19 02:26 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-15 16:55 UTCEPSS rescore
  15. 2026-07-15 01:57 UTCEPSS rescore
  16. 2026-07-13 06:10 UTCEPSS rescore
  17. 2026-07-13 06:10 UTCEPSS rescore
  18. 2026-07-12 23:38 UTCOSV refresh
  19. 2026-07-12 05:44 UTCEPSS rescore
  20. 2026-07-11 08:25 UTCEPSS rescore
  21. 2026-07-11 08:25 UTCEPSS rescore
  22. 2026-07-09 19:07 UTCEPSS rescore
  23. 2026-06-30 23:20 UTCEPSS rescore
  24. 2026-06-30 23:20 UTCEPSS rescore
  25. 2026-06-27 03:06 UTCEPSS rescore
Show 36 more
  1. 2026-06-27 03:06 UTCEPSS rescore
  2. 2026-06-25 13:48 UTCEPSS rescore
  3. 2026-06-24 14:03 UTCEPSS rescore
  4. 2026-06-24 14:03 UTCEPSS rescore
  5. 2026-06-24 09:29 UTCOSV refresh
  6. 2026-06-23 21:31 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-21 01:57 UTCEPSS rescore
  9. 2026-06-18 17:50 UTCEPSS rescore
  10. 2026-06-18 17:50 UTCEPSS rescore
  11. 2026-06-17 17:50 UTCEPSS rescore
  12. 2026-06-16 17:50 UTCEPSS rescore
  13. 2026-06-15 17:46 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-13 22:58 UTCEPSS rescore
  16. 2026-06-13 22:58 UTCEPSS rescore
  17. 2026-06-10 22:16 UTCEPSS rescore
  18. 2026-06-10 22:16 UTCEPSS rescore
  19. 2026-06-10 13:20 UTCEPSS rescore
  20. 2026-06-07 13:30 UTCOSV refresh
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 22:45 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-01 13:50 UTCEPSS rescore
  28. 2026-06-01 13:50 UTCEPSS rescore
  29. 2026-05-31 00:15 UTCEPSS rescore
  30. 2026-05-31 00:15 UTCEPSS rescore
  31. 2026-05-29 13:42 UTCEPSS rescore
  32. 2026-05-28 13:43 UTCEPSS rescore
  33. 2026-05-28 13:43 UTCEPSS rescore
  34. 2026-05-26 07:17 UTCEPSS rescore
  35. 2026-05-26 07:17 UTCEPSS rescore
  36. 2026-05-23 05:36 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2020/CVE-2020-26214.yaml
    First seen Jan 1, 2020

    Alerta < 8.1.0 - Authentication Bypass

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2020-26214?
CVE-2020-26214 is a critical vulnerability published on November 6, 2020. In Alerta before version 8.1.0, users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider. Only deployments where LDAP servers are configured to allow unauthenticated authentication mechanism for…
When was CVE-2020-26214 disclosed?
CVE-2020-26214 was first published in the National Vulnerability Database on November 6, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-26214 actively exploited?
CVE-2020-26214 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-26214?
CVE-2020-26214 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2020-26214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-26214, 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-2020-26214

Explore →

Is Your Infrastructure Affected by CVE-2020-26214?

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

Start Free Scan →Browse All CVEs