CVE-2026-44251

Wazuh : size_t underflow in msgs.c ReadSecMSG causes wazuh-remoted DoS and potential heap overflow via crafted agent message

Published Jul 17, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 3.0.0 and above, prior to 4.14.5, a size_t integer underflow in os_crypto/shared/msgs.c:389 allows any enrolled Wazuh agent to crash the wazuh-remoted process on the manager, immediately disconnecting all agents from the manager. A second code path reached by the same underflow may allow heap memory corruption. This issue has been fixed in version 4.14.5.

Analysis

AI-generated

Technical impact

A size_t underflow in os_crypto shared msgs.c allows any enrolled Wazuh agent to send a crafted message that causes the wazuh-remoted daemon on the manager to crash, immediately disconnecting all connected agents. This denial of service results from the buffer overrun flaw identified as CWE-122 and the integer underflow classified as CWE-191. A second code path reached by the same underflow may lead to heap memory corruption, which could compromise the integrity of the manager process if successfully exploited, but the CVE does not confirm that such corruption results in arbitrary code execution.

Affected Systems

The vulnerability affects the Wazuh platform, specifically versions 3.0.0 through 4.14.4. Wazuh is an open‑source threat prevention, detection, and response system used by many organizations for centralized log management and security monitoring.

Risk and Exploitability

The CVSS score is 6.5, indicating a moderate severity level. The EPSS score is below 1%, suggesting a low probability of exploitation in the wild, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector involves an uninhibited agent sending a crafted message to the manager over, which is typically internal to the organization’s network. The impact is primarily a service outage, but the presence of a heap corruption path raises the potential risk for more damaging exploitation if an attacker can succeed in triggering the overflow.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Wazuh to version 4.14.5 removes the size_t underflow and the heap corruption vectors
  • Restrict agent communication to trusted internal networks or place the wazuh-remoted service behind a firewall that limits inbound agent messages while the patch is pending
  • Configure high‑availability or fail‑over mechanisms for wazuh-remoted to maintain service availability if a crash occurs

Generated by OpenCVE AI on July 31, 2026 at 00:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', '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. In versions 3.0.0 and above, prior to 4.14.5, a size_t integer underflow in os_crypto/shared/msgs.c:389 allows any enrolled Wazuh agent to crash the wazuh-remoted process on the manager, immediately disconnecting all agents from the manager. A second code path reached by the same underflow may allow heap memory corruption. This issue has been fixed in version 4.14.5.
Title Wazuh : size_t underflow in msgs.c ReadSecMSG causes wazuh-remoted DoS and potential heap overflow via crafted agent message
Weaknesses CWE-122
CWE-191
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-122

    Heap-based Buffer Overflow

  • CWE-191

    Integer Underflow (Wrap or Wraparound)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 6:06 PM
Reserved
May 5, 2026, 4:33 PM
Status
Analyzed
Published
Jul 17, 2026, 2:18 AM
Modified
Jul 20, 2026, 2:22 AM