CVE-2026-46343

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, WazuhCommon.end_receiving_file() in framework/wazuh/core/cluster/common.py allows a cluster-authenticated node to delete files outside WAZUH_PATH. A syn_i_w_m_e request with an unknown task_id reaches the cleanup branch, where an attacker-controlled filename is passed to os.path.join without canonicalization or confinement. Absolute paths and traversal sequences can therefore target files such as ossec.conf, jwt_secret.json, TLS certificates, and ruleset files that are accessible to the Wazuh manager process. Deletion can disable the manager, invalidate API tokens, or disrupt cluster and API connectivity. This issue is fixed in versions 4.14.6 and 5.0.0-beta2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track*)
EG Risk 50/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit, github_pr.
github Patch Available🟡 PoC Available

Arbitrary File Deletion via Cluster Protocol – Incomplete Path Validation in end_receiving_file() · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-cqvw-w2rg-327f
github_release Patch Available

Wazuh v5.0.0 Beta 2

Patch available: wazuh/wazuh v5.0.0-beta2 (pre-release)

https://github.com/wazuh/wazuh/releases/tag/v5.0.0-beta2
github_release Patch Available

Wazuh v4.14.6

Patch available: wazuh/wazuh v4.14.6

https://github.com/wazuh/wazuh/releases/tag/v4.14.6
github_pr Patch Available

Improve cluster file handling path validation in end_receiving_file

Patch available: wazuh/wazuh v5.0.0-beta2 (PR #36060 merged 2026-05-13)

https://github.com/wazuh/wazuh/pull/36060
github_commit Patch Available

commit 90d43547d166 (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta2 (contains commit 90d43547d166)

https://github.com/wazuh/wazuh/commit/90d43547d166cdbe65e9a3d011f946214df9179c

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 01:55 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 21:06 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 23:28 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 14:56 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 17:17 UTCEG score recompute
  11. 2026-08-23 08:51 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 00:24 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 02:46 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 05:08 UTCEG score recompute
  18. 2026-08-19 18:18 UTCEG score recompute
  19. 2026-08-19 17:53 UTCEG score recompute
  20. 2026-08-19 16:24 UTCEG score recompute
  21. 2026-08-19 16:12 UTCEG score recompute
  22. 2026-08-19 16:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-46343?
CVE-2026-46343 is a high vulnerability published on August 19, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.0.0 until 4.14.6 and 5.0.0-beta2, WazuhCommon.endreceivingfile() in framework/wazuh/core/cluster/common.py allows a cluster-authenticated node to delete files outside WAZUHPATH. A syniwme request…
When was CVE-2026-46343 disclosed?
CVE-2026-46343 was first published in the National Vulnerability Database on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46343 actively exploited?
CVE-2026-46343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46343?
CVE-2026-46343 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-46343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46343, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-46343

Explore →

Is Your Infrastructure Affected by CVE-2026-46343?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.