Is CVE-2026-41424 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41424 being exploited in the wild.

How severe is CVE-2026-41424?

High severity, with a CVSS score of 8.2, published 19 August 2026.

Which products and versions are affected?

Wazuh 4.9.0 to 4.10.3, 4.14.0 to 4.14.5.

Is there a fix for CVE-2026-41424?

A patch was published on 2026-08-19: Fixed in versions 4.10.4 and 4.14.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41424 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-41424?

Check whether you run Wazuh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41424: Wazuh authentication bypass in user password update

CVE-2026-41424 · Severity: high · CVSS 8.2 · Published 2026-08-19

Wazuh is an open-source security platform used to detect and respond to threats across IT environments. An authenticated attacker with administrative privileges can bypass protections on critical system accounts and reset the password of the Wazuh superuser, gaining complete control over the security platform and all monitored systems. This could allow an attacker to disable security monitoring, extract sensitive data, or manipulate security alerts.

Technologies: Wazuh. Vendors: Wazuh.

Quick answers

Is CVE-2026-41424 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41424 being exploited in the wild.
How severe is CVE-2026-41424?: High severity, with a CVSS score of 8.2, published 19 August 2026.
Which products and versions are affected?: Wazuh 4.9.0 to 4.10.3, 4.14.0 to 4.14.5.
Is there a fix for CVE-2026-41424?: A patch was published on 2026-08-19: Fixed in versions 4.10.4 and 4.14.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41424 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-41424?: Check whether you run Wazuh at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is an authentication bypass in the PUT /security/users/{user_id} endpoint (api/api/controllers/security_controller.py). The endpoint incorrectly passes request.get("user") instead of the authenticated user's token (request.context['token_info']['sub']) to the authorization logic. The remove_nones_to_dict() function then strips out the resulting None value, preventing the reserved-account protection in framework/wazuh/security.py from validating who initiated the request. An authenticated user with the users_admin role can exploit this to overwrite passwords of protected administrator accounts (user IDs ≤99), including the Wazuh superuser account. The vulnerability affects versions 4.9.0 through 4.10.3 and 4.14.0 through 4.14.5; patches are available in versions 4.10.4 and 4.14.6.

Affected products

Wazuh Wazuh 4.9.0 to 4.10.3, 4.14.0 to 4.14.5

Timeline

2026-08-19: disclosed
2026-08-19: patched: Fixed in versions 4.10.4 and 4.14.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.