CVE-2026-61802

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (53rd 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

Also known asEUVD-2026-67358 (ENISA EUVD)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.7%CVSS: 6.5Exploit: No code on recordExposed 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.14.0 through 4.14.6, a low-privilege API user can read the cleartext cluster key from a configuration endpoint that fails to redact it. The REST API provides a masking control, mask_sensitive_config, that redacts sensitive fields such as authd.pass and cluster.key from configuration responses for users who lack update-config permission, and every config-read endpoint carries this decorator except GET /cluster/local/config. That endpoint, backed by read_config_wrapper, is gated only by cluster:read and returns the local node's cluster configuration including the cleartext key, whereas its siblings return the same value masked. As a result, any account with the default readonly or cluster_readonly role, which is explicitly denied update-config precisely so it cannot view secrets, receives the real cluster key. Because the cluster key authenticates and encrypts traffic between cluster nodes, disclosing it to an unprivileged account provides the authentication precondition for the cluster-peer remote code execution chains established by prior advisories. This issue is fixed in version 4.14.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

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 public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 27, 2026

Last Modified

September 15, 2026

Advisory Details (2)

Auto-updated Aug 28, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 1c55af25ebb1 (wazuh/wazuh)

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

https://github.com/wazuh/wazuh/commit/1c55af25ebb160bddbde591efc19bb77b01282e7
GitHub advisoryMentions a patch (unverified)

Cluster authentication key disclosed to low-privilege cluster:read API users via GET /cluster/local/config (missing mask_sensitive_config) — enables cluster-peer RCE chain · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-chmg-89pf-2q82

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 112 rows 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. None are among the latest 100 rows. The 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-61802?
CVE-2026-61802 is a medium-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.14.0 through 4.14.6, a low-privilege API user can read the cleartext cluster key from a configuration endpoint that fails to redact it. The REST API provides a…
When was the CVE record for CVE-2026-61802 published?
The CVE record for CVE-2026-61802 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-61802 actively exploited?
CVE-2026-61802 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61802?
CVE-2026-61802 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61802?
A fix for CVE-2026-61802 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-61802

Explore →

Is Your Infrastructure Affected by CVE-2026-61802?

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