Skip to content
Tuesday, October 13, 2026AboutContactRSS
Vulnerabilities

High-Severity Path Traversal Flaw in wazuh-manager Tracked as CVE-2026-74043

A newly published high vulnerability in wazuh-manager carries a CVSS score of 8.5. Here is what is affected and how to respond.

Illustration: A sleek black security management server sits on a clean desk, its front panel displaying blank status lights.
AI-generated illustration: Threat Times

Key points

  • CVE-2026-74043 affects wazuh-manager.
  • CVSS 8.5 (High).
  • No exploitation confirmed yet.

wazuh-manager is affected by CVE-2026-74043, a path traversal that the National Vulnerability Database rates 8.5 out of 10.

At a glance

CVE
CVE-2026-74043
Product
wazuh-manager
CVSS
8.5 High
Weakness
path traversal
Exploited
No known exploitation

What is the vulnerability?

The NVD entry states: Wazuh from 4.1.1 before 4.14.8 contains a path traversal vulnerability in upload_list_file, upload_rule_file, and upload_decoder_file that allows malicious cluster workers to write files at arbitrary paths. Attackers holding the cluster key can send DistributedAPI requests with ../ sequences in filename, bypassing REST controller validation, to write files as the wazuh user.

Affected versions

VendorProductVersions
Wazuhwazuh-managerbefore 4.14.8

Is it being exploited?

There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.

What should you do?

  • Identify whether the affected product and versions run in your environment.
  • Apply the vendor update listed in the advisory as soon as it is available.
  • Limit network exposure of the affected service until it is patched.
  • Monitor the vendor advisory for updated guidance or exploitation reports.

What to do and how to stay safe: CVE-2026-74043

  • Patch scores alone ignore context like network exposure and asset criticality.
  • You must map vulnerabilities to specific business risks to prioritize correctly.
  • Continuous exposure data replaces static scanning for accurate prioritization.

Prioritize vulnerabilities by actual exploitability and business impact, not by theoretical severity scores. Update your asset context and exposure data continuously to maintain accurate risk rankings.

Step-by-step guide: Risk Based Vulnerability Management: Prioritize Fixes by Actual Threat

General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is CVE-2026-74043?

CVE-2026-74043 is a path traversal vulnerability in wazuh-manager.

How severe is CVE-2026-74043?

It has a CVSS score of 8.5 High.

Is CVE-2026-74043 being exploited?

There is no public confirmation of exploitation at the time of publication.

Sources

  1. NVD — CVE-2026-74043
  2. Reference
  3. Reference
  4. Reference
CVE-2026-74043wazuh-managerHigh severity
Related articles