# CVE-2026-54083: Wazuh ip-customblock path traversal in active response

Source: https://junglewise.ai/threats/cve-2026-54083-wazuh-ip-customblock-path-traversal-in-active-response  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-28. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-54083 · Severity: high · CVSS 8.1 · Published 2026-08-28

Wazuh is an open-source security platform that monitors endpoints and cloud workloads for threats. Its ip-customblock active response script contains a path traversal vulnerability that allows attackers to create or delete arbitrary files on the system with root privileges. An attacker who can generate specially crafted security alerts can exploit this to delete critical system files (like password databases or SSH keys) or create disruptive files, potentially compromising the entire system's security and availability.

Technologies: [Wazuh](https://junglewise.ai/threats/technologies/wazuh). Vendors: [Wazuh](https://junglewise.ai/threats/vendors/wazuh).

## Quick answers

**Is CVE-2026-54083 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-54083 being exploited in the wild.

**How severe is CVE-2026-54083?** High severity, with a CVSS score of 8.1, published 28 August 2026.

**Which products and versions are affected?** Wazuh 4.2.0 to 4.14.6.

**Is there a fix for CVE-2026-54083?** A patch was published on 2026-08-18: Version 4.14.7 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-54083 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-54083?** Check whether you run Wazuh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is a path traversal (CWE-22) in the ip-customblock.c active response script. The script constructs file paths by concatenating the srcip field from alert JSON directly into a fixed /ipblock/ directory without validating the IP address format. An attacker can inject directory traversal sequences (../) in the srcip field to escape the intended directory and reach arbitrary filesystem paths. The active response daemon runs as root, allowing both arbitrary file creation (via append mode in ADD_COMMAND) and deletion (via remove() in DELETE_COMMAND). The fix, available in version 4.14.7, adds IP address validation using get_ip_version() to reject malformed input, matching the pattern already used in sibling scripts like host-deny.c.

## Affected products

- Wazuh Wazuh 4.2.0 to 4.14.6

## Timeline

- 2026-08-28: disclosed
- 2026-08-18: patched: Version 4.14.7 released with fix

## References

- [https://github.com/wazuh/wazuh/commit/e6ef99025b2ca4ba8003efb591c51545006bc2d4](https://github.com/wazuh/wazuh/commit/e6ef99025b2ca4ba8003efb591c51545006bc2d4)
- [https://github.com/wazuh/wazuh/security/advisories/GHSA-m4mf-qmhf-8vj6](https://github.com/wazuh/wazuh/security/advisories/GHSA-m4mf-qmhf-8vj6)

## Related threats

- [Wazuh heap buffer overflow in Windows EventChannel decoder](https://junglewise.ai/threats/cve-2026-62365-wazuh-is-an-open-source-security-platform-providing-unified-xdr)
- [Wazuh unauthenticated memory exhaustion in cluster listener](https://junglewise.ai/threats/cve-2026-71540-wazuh-is-an-open-source-security-platform-providing-unified-xdr)
- [Wazuh stack exhaustion in XML parser via element attributes](https://junglewise.ai/threats/cve-2026-61811-wazuh-is-an-open-source-security-platform-providing-unified-xdr)
- [Wazuh cluster key disclosure in GET /cluster/local/config](https://junglewise.ai/threats/cve-2026-61802-wazuh-cluster-key-disclosure-in-get-cluster-local-config)
- [Wazuh arbitrary file write in cluster worker file sync](https://junglewise.ai/threats/cve-2026-61800-wazuh-arbitrary-file-write-in-cluster-worker-file-sync)