CVE-2026-44255

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 64% 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, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, AuthenticationManager.check_user() in framework/wazuh/rbac/orm.py performs check_password_hash() only when the supplied username exists. A nonexistent username returns immediately, while a valid username causes an expensive bcrypt calculation. An unauthenticated remote attacker can compare authentication response times to enumerate valid Wazuh usernames and use that information in subsequent credential attacks. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 25, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Wazuh v5.0.0 Beta 2

Patch available: wazuh/wazuh v5.0.0-beta2 (pre-release)

https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2
github_release Patch Available

Wazuh v4.14.6

Patch available: wazuh/wazuh v4.14.6

https://github.com/wazuh/wazuh/releases/tag/v4.14.6
github_commit Patch Available

commit 5ecea7b38b99 (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta2 (contains commit 5ecea7b38b99)

https://github.com/wazuh/wazuh/commit/5ecea7b38b998407cb0d205467dd247140a0f981
github_pr Patch Available

Add cluster validations

Patch available: wazuh/wazuh v5.0.0-beta2 (PR #35757 merged 2026-04-28)

https://github.com/wazuh/wazuh/pull/35757
github Patch Available🟡 PoC Available

Username Enumeration via Timing Side-Channel · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-3978-44q9-9px9

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× 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-26 05:26 UTCEG score recompute
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 03:22 UTCEG score recompute
  4. 2026-08-25 02:45 UTCEG score recompute
  5. 2026-08-24 01:41 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 23:37 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 21:32 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:23 UTCEG score recompute
  12. 2026-08-19 16:22 UTCEG score recompute
  13. 2026-08-19 16:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-44255?
CVE-2026-44255 is a medium vulnerability published on August 19, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, AuthenticationManager.checkuser() in framework/wazuh/rbac/orm.py performs checkpassword_hash() only when the supplied username exists. A nonexistent username…
When was CVE-2026-44255 disclosed?
CVE-2026-44255 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44255 actively exploited?
CVE-2026-44255 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 63.6% of all scored CVEs.
What is the CVSS score of CVE-2026-44255?
CVE-2026-44255 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44255?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44255, 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

Explore the affected products and dependency analysis for CVE-2026-44255

Explore →

Is Your Infrastructure Affected by CVE-2026-44255?

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

Start Free Scan →Browse All CVEs