CVE-2026-74035

What it is

Wazuh versions from 4.6.0 before 4.14.8 contain an authentication bypass vulnerability where security.update_user places the reserved user guard and password policy inside a falsy truthiness check. A delegated user administrator can send an empty password to the user update endpoint, bypassing the reserved user guard to take over the wazuh superuser account and authenticate with empty credentials.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-08-14 14:06 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-10-13 14:17 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-10-13 20:39 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 8.6 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-13 14:17 UTC

Last modified

2026-10-13 20:39 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 8.6

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

High

User interaction

None

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-74035.md and follow it. Check whether this project is affected by CVE-2026-74035. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge