# CVE-2026-44254: Wazuh: Stack Out-of-Bounds Write in remoted Decompression Path

> A stack out-of-bounds write in the Wazuh remoted daemon allows attackers to crash message processing and disrupt agent communications via crafted encrypted messages.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-9wm4-fp6c-hqgq

## What is CVE-2026-44254?

CVE-2026-44254 is a medium-severity memory corruption vulnerability in Wazuh Wazuh, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 1.0.0 until 4.14.6 and 5.0.0-beta2, HandleSecureMessage() in src/remoted/secure.c passes a pointer inside its stack buffer to ReadSecMSG(), and src/os_crypto/shared/msgs.c decompresses up to OS_MAXSTR bytes at that offset. For an encrypted agent message on TCP port 1514 that expands to 65,536 bytes, os_zlib_uncompress() writes a terminating null byte beyond the end of the destination buffer. The resulting stack out-of-bounds write in the root-level remoted daemon can crash message processing and disrupt agent communications. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.

Weakness: CWE-787 (Out-of-bounds Write), CWE-131 (Incorrect Calculation of Buffer Size)

## Which versions are affected by CVE-2026-44254?

It affects 1 product.


Products: Wazuh Wazuh.

## How do I fix CVE-2026-44254?

No fix has been published for CVE-2026-44254 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44254 being exploited?

There is no known exploitation of CVE-2026-44254 in the wild and no public exploit code.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44254 and fix it if it is affected.

What it is: CVE-2026-44254 is a medium-severity memory corruption vulnerability in Wazuh Wazuh, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44254 in the wild and no public exploit code.

Affected product: Wazuh Wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44254/ (Markdown: https://insights.sbomify.com/CVE-2026-44254/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44254
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44254
- OSV: https://osv.dev/vulnerability/CVE-2026-44254

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44254/
Summaries are generated and may contain mistakes; the official description above is the record.