CVE-2026-26206Public exploitNetwork attack vector

Brute-force protection bypass via login counter race

Published Apr 29, 2026 · Updated Apr 29, 2026

Authentication rate-limit bypass in Wazuh 4.0.0 through 4.14.3 allows remote attackers to exceed password-guess limits via concurrent logins. The prevent_bruteforce_attack function checks and updates the shared ip_stats and ip_block collections without atomic synchronization, so parallel requests pass the limit check before their counters are updated. Exploitation requires network access to the server API and a valid username; it permits extra password guesses but does not itself disclose credentials or guarantee account access.

CVSS severity6.5
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Authentication rate-limit bypass in Wazuh 4.0.0 through 4.14.3 allows remote attackers to exceed password-guess limits via concurrent logins. The prevent_bruteforce_attack function checks and updates the shared ip_stats and ip_block collections without atomic synchronization, so parallel requests pass the limit check before their counters are updated. Exploitation requires network access to the server API and a valid username; it permits extra password guesses but does not itself disclose credentials or guarantee account access.

The record

CVE
CVE-2026-26206
Published
Apr 29, 2026
Updated
Apr 29, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-362, CWE-367, CWE-307, T1110.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 29, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 29, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.0.0, < 4.14.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.0.0, < 4.14.4

Published CVSS scores

6.5GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-362Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
CWE-307Improper Restriction of Excessive Authentication Attempts
T1110.001Password Guessing

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo