CVE-2026-46343

HIGHNVD 7.27.2
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
7.2EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.2Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.2
EG Score
7.2HIGHmedium confidence
EG Risk
48
EG Risk 48/100

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 (value × EchelonGraph’s weight)
Severity72% × 45%
The EG Score, 7.2 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 19, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Aug 19, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
GitHub advisoryMentions a patch (unverified)

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 pull request 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 12× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-12 16:03 UTCEG score recompute
  4. 2026-10-11 19:45 UTCEG score recompute
  5. 2026-10-11 17:00 UTCEG score recompute
  6. 2026-10-11 14:25 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-10-08 08:24 UTCEG score recompute
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-06 18:49 UTCEG score recompute
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-06 07:58 UTCEG score recompute
  16. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-05 01:46 UTCEG score recompute
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-03 16:56 UTCEG score recompute
  20. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-02 21:37 UTCEG score recompute
  22. 2026-10-01 22:47 UTCEG score recompute
  23. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-30 20:35 UTCEG score recompute
  25. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 more
  1. 2026-09-30 08:46 UTCEG score recompute
  2. 2026-09-28 21:43 UTCEG score recompute
  3. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-09-27 17:48 UTCEG score recompute
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  6. 2026-09-27 06:59 UTCEG score recompute
  7. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-09-24 19:45 UTCEG score recompute
  9. 2026-09-23 20:09 UTCEG score recompute
  10. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-09-22 19:50 UTCEG score recompute
  12. 2026-09-22 05:39 UTCEG score recompute
  13. 2026-09-20 21:10 UTCEG score recompute
  14. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-09-19 23:32 UTCEG score recompute
  16. 2026-09-19 01:53 UTCEG score recompute
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-09-18 15:03 UTCEG score recompute▼ 0.30
  19. 2026-09-18 15:02 UTCNVD updateCVSS v3 → 7.2
  20. 2026-09-17 21:32 UTCEG score recompute
  21. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-09-16 20:07 UTCEG score recompute
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-16 06:17 UTCEG score recompute
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-09-15 08:40 UTCEG score recompute
  27. 2026-09-14 00:12 UTCEG score recompute
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-09-12 15:45 UTCEG score recompute
  30. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-11 18:06 UTCEG score recompute
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  33. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-09-10 09:39 UTCEG score recompute
  35. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  36. 2026-09-09 02:36 UTCEG score recompute
  37. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-09-08 02:31 UTCEG score recompute
  39. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  40. 2026-09-06 17:32 UTCEG score recompute
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  42. 2026-09-05 19:54 UTCEG score recompute
  43. 2026-09-04 22:17 UTCEG score recompute
  44. 2026-09-04 11:26 UTCEG score recompute
  45. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  46. 2026-09-02 16:06 UTCEG score recompute
  47. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  48. 2026-09-01 17:33 UTCEG score recompute
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-09-01 06:41 UTCEG score recompute
  51. 2026-08-30 21:47 UTCEG score recompute
  52. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  53. 2026-08-30 10:58 UTCEG score recompute
  54. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  55. 2026-08-29 01:55 UTCEG score recompute
  56. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  57. 2026-08-27 21:06 UTCEG score recompute
  58. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  59. 2026-08-26 23:28 UTCEG score recompute
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  61. 2026-08-25 14:56 UTCEG score recompute
  62. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  63. 2026-08-24 17:17 UTCEG score recompute
  64. 2026-08-23 08:51 UTCEG score recompute
  65. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  66. 2026-08-22 00:24 UTCEG score recompute
  67. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  68. 2026-08-21 02:46 UTCEG score recompute
  69. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  70. 2026-08-20 05:08 UTCEG score recompute
  71. 2026-08-19 18:18 UTCEG score recompute
  72. 2026-08-19 17:53 UTCEG score recompute
  73. 2026-08-19 16:24 UTCEG score recompute
  74. 2026-08-19 16:12 UTCEG score recomputeFirst assessed: 7.5 HIGH
  75. 2026-08-19 16:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46343?
CVE-2026-46343 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-46343 published?
The CVE record for CVE-2026-46343 was published on August 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-46343 actively exploited?
CVE-2026-46343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46343?
CVE-2026-46343 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-46343?
A fix for CVE-2026-46343 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs