CVE-2026-61783

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (33rd 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
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.4%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, an authenticated low-privilege user can read the cluster secret from the manager configuration because the logic that masks sensitive values is disabled by any update-config RBAC rule, including an explicit deny. The mask_sensitive_config() decorator applies masking only when _has_update_permissions() returns false, but that gate treats a user as able to update the config whenever a  manager:update_config  or  cluster:update_config  rule exists, without ever checking whether the rule's effect is allow or deny. Because a deny rule is stored as a real entry, a read-only account that is hardened by explicitly denying config edits is counted as having update permission, which turns masking off. A single authenticated GET request to the configuration endpoint with  raw=true  then returns the verbatim ossec.conf XML with  cluster.key  in clear, whereas an otherwise identical account without the deny rule sees the value masked. This issue is fixed in version 4.14.7.

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 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)
Severity65% × 45%
The EG Score, 6.5 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 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.4%
EPSS %ILE
33rd
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 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.

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 27, 2026
Patch available. Sources: github, github_commit.
GitHub commit Patch Available

commit 939f2e52afff (wazuh/wazuh)

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

https://github.com/wazuh/wazuh/commit/939f2e52afff8fbeb7b0894f3f1417eb6c395db3
GitHub advisoryMentions a patch (unverified)

RBAC permission-effect check in mask_sensitive_config allows low-privilege users to read cluster.key · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-vjcq-cf36-f5gx

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61783?
CVE-2026-61783 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, an authenticated low-privilege user can read the cluster secret from the manager configuration because the logic that masks sensitive values is…
When was the CVE record for CVE-2026-61783 published?
The CVE record for CVE-2026-61783 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-61783 actively exploited?
CVE-2026-61783 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61783?
CVE-2026-61783 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-61783?
A fix for CVE-2026-61783 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-61783

Explore →

Is Your Infrastructure Affected by CVE-2026-61783?

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

Book a Demo →Browse All CVEs