CVE-2026-25769
CVE-2026-25769 is a critical-severity vulnerability in wazuh (CVSS 3.1 base score 9.1), classified as CWE-502 (Deserialization of Untrusted Data). It is not in the CISA Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment rates its exploitation as proof of concept. As of 2026-11-22, EPSS estimates a 10.0% probability of exploitation in the next 30 days, in the 95th percentile of scored CVEs.
Updated
- CVSS 3.1
- 9.1 CRITICAL
- EPSS
- 10.0% (95th pct)
- CISA KEV
- Not listed
- Published
- 2026-03-17
- Weakness
- CWE-502
Description
Wazuh is a free and open source platform used for threat prevention, detection, and response. Versions 4.0.0 through 4.14.2 have a Remote Code Execution (RCE) vulnerability due to Deserialization of Untrusted Data). All Wazuh deployments using cluster mode (master/worker architecture) and any organization with a compromised worker node (e.g., through initial access, insider threat, or supply chain attack) are impacted. An attacker who gains access to a worker node (through any means) can achieve full RCE on the master node with root privileges. Version 4.14.3 fixes the issue.
Key Findings
as of 2026-11-22- Its current EPSS score (10.0%) is higher than that of 24% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesIf CISA adds it to the KEV catalog: 3 days and forensic triage on a publicly exposed asset, 14 days on other assets.
Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (not listed) and CISA's SSVC values (automatable no, technical impact total, 2026-03-17).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised. Fix on system upgrade means remediating the next time the asset receives a scheduled major upgrade or rebuild.
If CISA adds the CVE to the KEV catalog, the timeline shortens.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| wazuh | wazuh wazuh | >= 4.0.0, < 4.14.3 |
References
2 linksRecord Details
- Published
- 2026-03-17
- Last updated
- 2026-03-18
- Assigner (CNA)
- GitHub_M
- Credited to
- -
More from wazuh
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.