CVE-2026-25771

Wazuh Vulnerable to Denial of Service via Synchronous I/O Blocking in Asynchronous Authentication Middleware

Published Mar 17, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.3.0 and prior to version 4.14.3, a Denial of Service (DoS) vulnerability exists in the Wazuh API authentication middleware (`middlewares.py`). The application uses an asynchronous event loop (Starlette/Asyncio) to call a synchronous function (`generate_keypair`) that performs blocking disk I/O on every request containing a Bearer token. An unauthenticated remote attacker can exploit this by flooding the API with requests containing invalid Bearer tokens. This forces the single-threaded event loop to pause for file read operations repeatedly, starving the application of CPU resources and potentially preventing it from accepting or processing legitimate connections. Version 4.14.3 fixes the issue.

Analysis

AI-generated

Technical impact

The vulnerability is caused by calling a synchronous disk I/O function (`generate_keypair`) inside an asynchronous event loop, which blocks the single‑threaded Starlette/Asyncio loop on every bearer‑token request. An attacker can flood the API with requests that include invalid bearer tokens, causing repeated blocking and starvations of CPU resources. The result is a denial of service that prevents legitimate connections from being handled. This weakness is classified as CWE‑400: Uncontrolled Resource Consumption.

Affected Systems

Affects the Wazuh platform (vendor: wazuh:wazuh). Versions starting at 4.3.0 up through 4.14.2 are vulnerable; the issue is fixed in 4.14.3 and later.

Risk and Exploitability

With a CVSS score of 5.3 and an EPSS score of less than 1 %, the vulnerability is unlikely to be widely exploited yet. It is not listed in the CISA KEV catalog. The attack vector is remote, unauthenticated, and relies on flooding the API with malformed bearer tokens to block the event loop.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Wazuh to version 4.14.3 or later to apply the vendor patch.
  • If an immediate upgrade is not feasible, inspect the application logs for excessive authentication requests and consider implementing request rate limiting or firewall rules to mitigate flood attempts.

Generated by OpenCVE AI on March 19, 2026 at 16:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Wazuh
Wazuh wazuh
Vendors & Products Wazuh
Wazuh wazuh
Type Values Removed Values Added
Description Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.3.0 and prior to version 4.14.3, a Denial of Service (DoS) vulnerability exists in the Wazuh API authentication middleware (`middlewares.py`). The application uses an asynchronous event loop (Starlette/Asyncio) to call a synchronous function (`generate_keypair`) that performs blocking disk I/O on every request containing a Bearer token. An unauthenticated remote attacker can exploit this by flooding the API with requests containing invalid Bearer tokens. This forces the single-threaded event loop to pause for file read operations repeatedly, starving the application of CPU resources and potentially preventing it from accepting or processing legitimate connections. Version 4.14.3 fixes the issue.
Title Wazuh Vulnerable to Denial of Service via Synchronous I/O Blocking in Asynchronous Authentication Middleware
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 18, 2026, 1:37 PM
Reserved
Feb 5, 2026, 6:35 PM
Status
Analyzed
Published
Mar 17, 2026, 7:16 PM
Modified
Jun 17, 2026, 10:25 AM