CVE-2026-41424

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.9.0 until 4.10.4 and 4.14.6, PUT /security/users/{user_id} in api/api/controllers/security_controller.py passes request.get("user") instead of request.context['token_info']['sub'] as current_user. remove_nones_to_dict() removes the resulting None value, so the reserved-account protection in framework/wazuh/security.py cannot verify who is making the request. An authenticated user with the users_admin role can overwrite the password of protected administrator accounts with user IDs at or below 99, including the wazuh superuser, and gain full administrative control. This issue is fixed in versions 4.10.4 and 4.14.6.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
53
EG Risk 53/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)
Severity82% × 45%
The EG Score, 8.2 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.5%
EPSS %ILE
39th
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 19, 2026

Last Modified

September 18, 2026

Advisory Details (7)

Auto-updated Aug 19, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

Wazuh v4.14.6

Patch available: wazuh/wazuh v4.14.6

https://github.com/wazuh/wazuh/releases/tag/v4.14.6
GitHub release Patch Available

Wazuh v4.10.4

Patch available: wazuh/wazuh v4.10.4

https://github.com/wazuh/wazuh/releases/tag/v4.10.4
GitHub commit Patch Available

commit 813add3575ec (wazuh/wazuh)

Patch available: wazuh/wazuh v5.0.0-beta2 (contains commit 813add3575ec)

https://github.com/wazuh/wazuh/commit/813add3575ecd4df484b2326715ca78f65505b4e
GitHub commit Patch Available

commit 1a38d11574c6 (wazuh/wazuh)

Patch available: wazuh/wazuh v4.10.4 (contains commit 1a38d11574c6)

https://github.com/wazuh/wazuh/commit/1a38d11574c6d35a4272e1e7145d55d293e7dda4
GitHub pull request Patch Available

Backport: Validate current user in update-user endpoint to 4.10.4

Patch available: wazuh/wazuh v4.10.4 (PR #35469 merged 2026-04-16)

https://github.com/wazuh/wazuh/pull/35469
GitHub pull request Patch Available

Validate current user in update-user endpoint

Patch available: wazuh/wazuh v5.0.0-beta2 (PR #35442 merged 2026-04-15)

https://github.com/wazuh/wazuh/pull/35442
GitHub advisoryMentions a patch (unverified)

Privilege Escalation via Admin-Protection Bypass in update-user API Endpoint · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-gj9h-8hmr-xjjr

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41424?
CVE-2026-41424 is a high-severity vulnerability; its CVE record was published on August 19, 2026. Wazuh is a free and open source platform used for threat prevention, detection, and response. From 4.9.0 until 4.10.4 and 4.14.6, PUT /security/users/{userid} in api/api/controllers/securitycontroller.py passes request.get("user") instead of request.context['tokeninfo']['sub'] as currentuser.…
When was the CVE record for CVE-2026-41424 published?
The CVE record for CVE-2026-41424 was published on August 19, 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 18, 2026; the record at its source may have been updated since.
Is CVE-2026-41424 actively exploited?
CVE-2026-41424 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41424?
CVE-2026-41424 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41424?
A fix for CVE-2026-41424 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-41424

Explore →

Is Your Infrastructure Affected by CVE-2026-41424?

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

Book a Demo →Browse All CVEs