Skip to main content
VulnerabilityPublished Updated

CVE-2026-44255: wazuh · Timing Side Channel

Affects wazuhSource GCVE Database

0

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.0.0-beta2 or 4.14.6 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.0-beta2, 4.14.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade wazuh/wazuh to 5.0.0-beta2 or 4.14.6.

Affected software

ProductAffectedFixed in
GitHubwazuh/wazuhpkg:github/wazuh/wazuhOther threatsAffected
  • >=4.0.0 <4.14.6
  • >=5.0.0-beta1 <5.0.0-beta2
Fixed in
  • 4.14.6
  • 5.0.0-beta2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

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.

References

Community reviews

Loading reviews…