CVE-2026-41424Public exploitNetwork attack vector

Administrator takeover via missing current-user binding

Published Aug 19, 2026 · Updated Aug 19, 2026

Incorrect authorization in Wazuh 4.9.0 through 4.10.3 and 4.11.0 through 4.14.5 lets remote authenticated users overwrite protected admin passwords. PUT /security/users/{user_id} in api/api/controllers/security_controller.py passes current_user from request.get("user") instead of request.context['token_info']['sub'], and remove_nones_to_dict() drops the resulting None so the reserved-account check in framework/wazuh/security.py never executes. Reachability requires a valid account with the built-in users_admin role, after which IDs 1 through 99, including the wazuh superuser, can be reset and used for full administrative control.

CVSS severity8.2
High
EPSS probability0.41%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in Wazuh 4.9.0 through 4.10.3 and 4.11.0 through 4.14.5 lets remote authenticated users overwrite protected admin passwords. PUT /security/users/{user_id} in api/api/controllers/security_controller.py passes current_user from request.get("user") instead of request.context['token_info']['sub'], and remove_nones_to_dict() drops the resulting None so the reserved-account check in framework/wazuh/security.py never executes. Reachability requires a valid account with the built-in users_admin role, after which IDs 1 through 99, including the wazuh superuser, can be reset and used for full administrative control.

The record

CVE
CVE-2026-41424
Published
Aug 19, 2026
Updated
Aug 19, 2026
Vendor
Wazuh
Product
Wazuh
Classifications
CWE-863, T1098
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.11.0, < 4.14.6
  2. Affected versionversion=>=4.9.0, < 4.10.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Wazuh · Wazuhversion=>= 4.11.0, < 4.14.6; version=>=4.9.0, < 4.10.4

Published CVSS scores

8.2[email protected]CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization
T1098Account Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo