CVE-2020-26214

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 66% (99th percentile of EPSS-scored CVEs). 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.1EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS PROB: 66%CVSS: 9.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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
Severity91% × 45%
Exploitation66% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
66%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). 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

November 6, 2020

Last Modified

November 21, 2024

Advisory Details (6)

Auto-updated Jul 19, 2026
Patch available. Sources: github_commit, github_pr, github.
githubMentions a patch (unverified)

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 rangeFix by version rangeDependents
alerta-server3.1.2 ... 8.0.3 (230 versions)
  • 8.0.0 up to 8.1.0: fixed in 8.1.0
  • every version up to 7.5.7: fixed in 7.5.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 23× 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 110 total refreshes for this CVE.

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

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2020/CVE-2020-26214.yaml
    Published Nov 7, 2020

    Alerta < 8.1.0 - Authentication Bypass

    Open source ↗

Related CVEs(same product + same CWE)

Same product

1 shown

PyPI:alerta-server

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 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 66% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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?
A fix for CVE-2020-26214 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs