dbcve.org
WazuhApplication

CVE-2026-30893

CRITICAL · 9.9 CVSS v3.1 Published 2026-04-29
Fix available
A fix is available. Upgrade to 4.14.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.4.0 to before version 4.14.4, a path traversal vulnerability in Wazuh's cluster synchronization extraction routine allows an authenticated cluster peer to write arbitrary files outside the intended extraction directory on other cluster nodes. This can be escalated to code execution in the Wazuh service context by overwriting Python modules loaded by Wazuh components (proof of concept available as separate attachment). In deployments where the cluster daemon runs with elevated privileges, system-level compromise is possible. This issue has been patched in version 4.14.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability in Wazuh's cluster synchronization extraction routine (versions 4.4.0-4.14.3) allows an authenticated cluster peer to write arbitrary files outside the intended extraction directory. By overwriting Python modules loaded by Wazuh components, an attacker can achieve code execution within the Wazuh service context, potentially leading to system-level compromise when the cluster daemon runs with elevated privileges.

MitigationUpgrade to Wazuh version 4.14.4 or later. In the interim, restrict cluster peer authentication and minimize privileges granted to the cluster daemon.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WazuhApplication
Affected:>= 4.4.0, < 4.14.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Wazuh version
    Run `wazuh-control info` or check `/var/ossec/` for version file. Also check via API endpoint `/manager/version`.
    Affected if Version is 4.4.0 through 4.14.3 inclusive, meaning the vulnerable cluster sync code is present.
  2. Verify if Wazuh cluster mode is enabled
    Check for cluster configuration in `/var/ossec/etc/ossec.conf` under the <cluster> section, or query the Wazuh API at `/cluster/status`.
    Affected if Cluster mode is enabled and the vulnerable synchronization extraction routine is in use.
  3. Confirm cluster authentication settings
    Inspect the cluster configuration for `<auth>` or `<node>` sections that define peer authentication. Check if password-based or SSL authentication is configured in `ossec.conf`.
    Affected if Cluster peer authentication is enabled or accessible, allowing authenticated peers to trigger the extraction routine.
  4. Inspect cluster worker configuration
    Check `/var/ossec/etc/ossec.conf` for worker node definitions. Verify if this node accepts incoming cluster connections from other peers.
    Affected if This node is configured as a worker that receives files from the cluster, making it a potential target.

The environment is affected if Wazuh version is between 4.4.0 and 4.14.3, cluster mode is enabled, and the node accepts authenticated cluster peer connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.14.4 or later
Fixed in 4.14.4
Interim mitigation

Upgrade to Wazuh version 4.14.4 or later. In the interim, restrict cluster peer authentication and minimize privileges granted to the cluster daemon.

Recommended fix High confidence

4.14.4

  1. Back up the current Wazuh configuration and data directory before starting the upgrade
  2. Stop all Wazuh services (wazuh-manager, wazuh-agent, etc.) to ensure a clean upgrade process
  3. Upgrade Wazuh to version 4.14.4 or later by using the official Wazuh upgrade procedure for your installation method (packages, Docker, or source)
  4. After upgrade completion, verify the installed Wazuh version is 4.14.4 or higher using the command: wazuh-control info or check the Wazuh dashboard about section
  5. Restart Wazuh services to load the patched components
  6. Verify the cluster synchronization functionality works correctly and no errors appear in the logs related to file extraction
Caveat Review the Wazuh 4.14.4 release notes for any configuration or feature changes that may affect your deployment before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wazuh Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30893 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data