CVE-2026-54083 Wazuh: Path traversal in ip-customblock active response allows arbitrary file creation and deletion

High 8.1 Published Updated

Attackers can create or delete arbitrary files as root via path traversal in the ip-customblock active response script, potentially compromising system integrity.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-54083?

CVE-2026-54083 is a high-severity path traversal vulnerability in Wazuh Wazuh, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. The  ip-customblock  active response script contains a path traversal vulnerability that lets an attacker create or delete arbitrary files on the filesystem as root. The script builds a file path by concatenating the  srcip  field taken from alert JSON directly onto the fixed  /ipblock/  base directory, without validating that the value is a well-formed IP address. Because the extraction routine returns the raw string unchecked, an attacker who can trigger alert-matching log events with a crafted  srcip  containing  ../  sequences can escape the base directory. The block action opens the resulting path in append mode, creating an empty file at an arbitrary location, while the unblock action passes it to remove(), deleting an arbitrary file; since the active response daemon runs as root, this includes sensitive files such as system credentials and Wazuh configuration. Unlike the sibling scripts host-deny.c, default-firewall-drop.c, and firewalld-drop.c, which reject non-IP input via get_ip_version(), ip-customblock.c omits this validation. This issue is fixed in version 4.14.7.

Weakness: CWE-22

Which versions are affected by CVE-2026-54083?

It affects 1 product.

Products include Wazuh Wazuh.

How do I fix CVE-2026-54083?

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

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-54083 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54083 exists.

All Wazuh Wazuh vulnerabilities

Sources

Also known as GHSA-m4mf-qmhf-8vj6.

Is CVE-2026-54083 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free