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% (35th 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

Also known asEUVD-2026-67308 (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.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 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.4%
EPSS %ILE
35th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% 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 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 7× in last 7d / 31× 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 117 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 17 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.4% · 35th percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  4. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  5. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  7. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  8. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  9. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  11. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  12. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  13. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-30 09:25 UTCOSV refresh
  16. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  19. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-25 14:14 UTCEchelonGraph re-scored
  22. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-22 19:56 UTCEchelonGraph re-scored
  25. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 more
  1. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-18 03:25 UTCEchelonGraph re-scored
  6. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-12 15:50 UTCEchelonGraph re-scored
  13. 2026-10-11 19:34 UTCEchelonGraph re-scored
  14. 2026-10-11 16:49 UTCEchelonGraph re-scored
  15. 2026-10-11 14:11 UTCEchelonGraph re-scored
  16. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-10 01:44 UTCEchelonGraph re-scored
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-10-08 09:13 UTCEchelonGraph re-scored
  22. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  23. 2026-10-07 08:45 UTCEchelonGraph re-scored
  24. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-10-06 08:08 UTCEchelonGraph re-scored
  26. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  27. 2026-10-05 07:41 UTCEchelonGraph re-scored
  28. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  29. 2026-10-04 07:13 UTCEchelonGraph re-scored
  30. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  31. 2026-10-03 06:46 UTCEchelonGraph re-scored
  32. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  33. 2026-10-02 06:18 UTCEchelonGraph re-scored
  34. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-10-01 05:30 UTCEchelonGraph re-scored
  36. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-09-30 04:22 UTCEchelonGraph re-scored
  38. 2026-09-28 21:12 UTCEchelonGraph re-scored
  39. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  40. 2026-09-27 16:14 UTCEchelonGraph re-scored
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  42. 2026-09-26 15:47 UTCEchelonGraph re-scored
  43. 2026-09-25 00:36 UTCEchelonGraph re-scored
  44. 2026-09-24 00:07 UTCEchelonGraph re-scored
  45. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  46. 2026-09-22 23:40 UTCEchelonGraph re-scored
  47. 2026-09-21 22:52 UTCEchelonGraph re-scored
  48. 2026-09-20 22:25 UTCEchelonGraph re-scored
  49. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  50. 2026-09-19 21:56 UTCEchelonGraph re-scored
  51. 2026-09-18 21:29 UTCEchelonGraph re-scored
  52. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  53. 2026-09-17 20:53 UTCEchelonGraph re-scored
  54. 2026-09-16 19:44 UTCEchelonGraph re-scored
  55. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  56. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  57. 2026-09-15 19:16 UTCEchelonGraph re-scored▼ 0.50
  58. 2026-09-15 19:15 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  59. 2026-09-15 06:47 UTCEchelonGraph re-scored
  60. 2026-09-13 21:52 UTCEchelonGraph re-scored
  61. 2026-09-12 23:56 UTCEchelonGraph re-scored
  62. 2026-09-11 15:02 UTCEchelonGraph re-scored
  63. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  65. 2026-09-10 17:05 UTCEchelonGraph re-scored
  66. 2026-09-09 08:11 UTCEchelonGraph re-scored
  67. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  68. 2026-09-07 21:25 UTCEchelonGraph re-scored
  69. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  70. 2026-09-06 23:29 UTCEchelonGraph re-scored
  71. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  72. 2026-09-06 01:33 UTCEchelonGraph re-scored
  73. 2026-09-04 16:39 UTCEchelonGraph re-scored
  74. 2026-09-04 05:41 UTCEchelonGraph re-scored
  75. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile

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 (35th 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.