CVE-2026-39359

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (27th 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
Elevated
7.5EG
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.5Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 4.0.0 through 4.10.3 and 4.11.0 through 4.14.4, a logic flaw affects the Wazuh Manager's enrollment daemon (authd) and synchronization daemon (remoted). The authd process allows agents to select a group during enrollment but does not filter path traversal sequences such as "..." While the manager checks for the group directory using wopendir(), the ".." sequence references the parent directory (/var/ossec/etc), allowing it to pass validation. After the malicious group is accepted and stored in the manager's global database, the remoted process uses this unchecked value to build paths for agent configuration synchronization. As a result, sensitive files from /var/ossec/etc, such as client.keys, ossec.conf, and internal certificates, are included in the agent's shared configuration stream and exposed to the attacker. This issue has been fixed in versions 4.10.4 and 4.14.5.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: The CVE record names the fixed release. 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
27th
KEV
Not listed

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

The CVE record names the fixed release. 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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 16, 2026

Last Modified

July 20, 2026

Advisory Details (1)

Auto-updated Jul 17, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated Path Traversal in Wazuh authd via Agent Group Name · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-6q95-fcwc-4h44

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 33× 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.

Showing the most recent 99 of 134 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 35 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-39359?
CVE-2026-39359 is a high-severity vulnerability; its CVE record was published on July 16, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 4.0.0 through 4.10.3 and 4.11.0 through 4.14.4, a logic flaw affects the Wazuh Manager's enrollment daemon (authd) and synchronization daemon (remoted). The authd process allows agents to…
When was the CVE record for CVE-2026-39359 published?
The CVE record for CVE-2026-39359 was published on July 16, 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 July 20, 2026; the record at its source may have been updated since.
Is CVE-2026-39359 actively exploited?
CVE-2026-39359 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-39359?
CVE-2026-39359 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-39359?
The CVE record for CVE-2026-39359 names the fix: "This issue has been fixed in versions 4.10.4 and 4.14.5."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-39359?

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

Book a Demo →Browse All CVEs