Skip to content

CVE-2026-41424

8.2 HIGHPublic exploitEPSS 0.41%
  1. Published19 Aug 2026

Description

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 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredHigh
User interactionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H

Affected products

Wazuh Wazuh≥ 4.11.0 < 4.14.6 · ≥ 4.9.0 < 4.10.4

Frequently asked

Is CVE-2026-41424 being actively exploited?

CVE-2026-41424 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.41%.

How severe is CVE-2026-41424?

CVE-2026-41424 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.41% probability of exploitation.

Which products are affected by CVE-2026-41424?

Affected products include Wazuh Wazuh.

How do I fix CVE-2026-41424?

Upgrade affected software to a fixed version, for example Wazuh Wazuh 4.14.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-41424 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.