CVE-2026-41424

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.2(medium)
EG Risk
53(Track)
EG Risk 53/100SSVC: Track

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
Severity82% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

August 19, 2026

Last Modified

August 21, 2026

Advisory Details (7)

Auto-updated Aug 19, 2026
🔬 Proof of concept available. 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_pr 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_pr 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 Patch Available🟡 PoC Available

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 / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-30 01:56 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 01:54 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 20:48 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 20:47 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 20:38 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-24 20:29 UTCEG score recompute
  12. 2026-08-23 08:23 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 08:23 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 20:23 UTCEG score recompute
  17. 2026-08-21 19:59 UTCEG score recompute
  18. 2026-08-21 05:24 UTCEG score recompute
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-19 17:23 UTCEG score recompute
  21. 2026-08-19 16:22 UTCEG score recompute
  22. 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 vulnerability 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 CVE-2026-41424 disclosed?
CVE-2026-41424 was first published in the National Vulnerability Database on August 19, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41424 actively exploited?
CVE-2026-41424 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.8% of all scored CVEs.
What is the CVSS score of CVE-2026-41424?
CVE-2026-41424 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-41424?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41424, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs