CVE-2026-61800

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.0% (61st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.4.0 through 4.14.6, a party holding the cluster key can write, overwrite, or delete arbitrary files under /var/ossec on worker nodes, leading to remote code execution as root. During cluster file synchronization, the non-merged branch of update_master_files_in_worker() moves each staged file to a destination derived only from safe_join(), which confines the path to /var/ossec but never verifies that the file lands in the directory declared by its cluster_item_key. Because the destination check present on the primary node and on the worker's merged branch was not applied, a peer can place files at attacker-chosen locations under /var/ossec, including paths that are executed as root, and the delete branch has the same gap. This is an incomplete fix for CVE-2026-30893, which addressed traversal outside /var/ossec but left this path able to redirect files anywhere within it. This issue is fixed in version 4.14.7.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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.
EPSS PROB
1.0%
EPSS %ILE
61st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (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 27, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Incomplete fix for CVE-2026-30893: missing directory confinement in cluster worker file sync allows arbitrary file write under /var/ossec on worker nodes · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-3jff-488g-335f
GitHub commit Patch Available

commit f7f7c4d2d9e6 (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta3 (contains commit f7f7c4d2d9e6)

https://github.com/wazuh/wazuh/commit/f7f7c4d2d9e683c5d42e997fe7028a3fb2578853

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 54× 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-14 09:26 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  3. 2026-10-13 06:56 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  5. 2026-10-12 15:50 UTCEG score recompute
  6. 2026-10-11 19:34 UTCEG score recompute
  7. 2026-10-11 16:49 UTCEG score recompute
  8. 2026-10-11 14:11 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  11. 2026-10-10 01:43 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  13. 2026-10-09 02:51 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  15. 2026-10-08 01:10 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  17. 2026-10-06 18:39 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  19. 2026-10-05 20:32 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  21. 2026-10-04 23:26 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  23. 2026-10-03 14:56 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  25. 2026-10-02 21:31 UTCEG score recompute
Show 62 more
  1. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  2. 2026-10-01 19:51 UTCEG score recompute
  3. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  4. 2026-09-30 19:53 UTCEG score recompute
  5. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  6. 2026-09-29 16:08 UTCEG score recompute
  7. 2026-09-29 00:53 UTCEG score recompute
  8. 2026-09-28 13:56 UTCEG score recompute
  9. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  10. 2026-09-27 15:39 UTCEG score recompute
  11. 2026-09-26 19:28 UTCEG score recompute
  12. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.0% · 60th percentile
  13. 2026-09-26 15:47 UTCEG score recompute
  14. 2026-09-24 14:38 UTCEG score recompute
  15. 2026-09-23 20:11 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-22 18:21 UTCEG score recompute
  18. 2026-09-21 22:34 UTCEG score recompute
  19. 2026-09-20 23:40 UTCEG score recompute
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  21. 2026-09-19 17:24 UTCEG score recompute
  22. 2026-09-18 22:42 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  24. 2026-09-17 20:53 UTCEG score recompute
  25. 2026-09-16 14:28 UTCEG score recompute
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  27. 2026-09-16 06:53 UTCEG score recompute
  28. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-09-15 03:19 UTCEG score recompute
  30. 2026-09-13 17:28 UTCEG score recompute
  31. 2026-09-12 15:39 UTCEG score recompute
  32. 2026-09-11 17:28 UTCEG score recompute
  33. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  34. 2026-09-11 10:00 UTCEG score recompute
  35. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  36. 2026-09-10 11:51 UTCEG score recompute
  37. 2026-09-09 00:56 UTCEG score recompute
  38. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  39. 2026-09-07 19:27 UTCEG score recompute
  40. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  41. 2026-09-06 17:26 UTCEG score recompute
  42. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  43. 2026-09-05 15:36 UTCEG score recompute
  44. 2026-09-04 17:21 UTCEG score recompute
  45. 2026-09-04 06:11 UTCEG score recompute
  46. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  47. 2026-09-02 15:35 UTCEG score recompute
  48. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  49. 2026-09-01 17:13 UTCEG score recompute
  50. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  51. 2026-09-01 06:04 UTCEG score recompute
  52. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  53. 2026-08-30 20:47 UTCEG score recompute
  54. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-08-30 02:21 UTCEG score recompute
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  57. 2026-08-29 00:19 UTCEG score recompute
  58. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  59. 2026-08-28 20:38 UTCEG score recompute
  60. 2026-08-28 02:18 UTCEG score recompute
  61. 2026-08-28 02:11 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  62. 2026-08-28 02:07 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61800?
CVE-2026-61800 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. In versions 4.4.0 through 4.14.6, a party holding the cluster key can write, overwrite, or delete arbitrary files under /var/ossec on worker nodes, leading to remote code execution…
When was the CVE record for CVE-2026-61800 published?
The CVE record for CVE-2026-61800 was published on August 27, 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-61800 actively exploited?
CVE-2026-61800 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (61st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61800?
CVE-2026-61800 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61800?
A fix for CVE-2026-61800 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-61800

Explore →

Is Your Infrastructure Affected by CVE-2026-61800?

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

Book a Demo →Browse All CVEs