How severe is CVE-2026-25769?

CVE-2026-25769 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-25769 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 9% (95th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-25769?

CVE-2026-25769 affects Wazuh. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-25769?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-25769 have an EU (EUVD) identifier?

Yes. CVE-2026-25769 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-12595.

When was CVE-2026-25769 published?

CVE-2026-25769 was published on 2026-03-17 and last updated on 2026-06-17.

CVE-2026-25769

CVE-2026-25769 is a critical-severity vulnerability in Wazuh with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
EPSS exploit prediction: 9% (95th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-12595
Weakness: CWE-502
Affected product: Wazuh
Published: 2026-03-17
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-25769?: 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.
How severe is CVE-2026-25769?: CVE-2026-25769 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-25769 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 9% (95th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-25769?: CVE-2026-25769 affects Wazuh. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-25769?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-25769 have an EU (EUVD) identifier?: Yes. CVE-2026-25769 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-12595.
When was CVE-2026-25769 published?: CVE-2026-25769 was published on 2026-03-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:wazuh:wazuh:*:*:*:*:*:*:*:*

More vulnerabilities in Wazuh

CVE-2025-24016 — Critical (CVSS 9.9): Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0…
CVE-2024-32038 — Critical (CVSS 9.8): Wazuh is a free and open source platform used for threat prevention, detection, and response. There is a buffer…
CVE-2021-44079 — Critical (CVSS 9.8): In the wazuh-slack active response script in Wazuh 4.2.x before 4.2.5, untrusted user agents are passed to a curl…
CVE-2026-25770 — Critical (CVSS 9.1): Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 3.9.0…
CVE-2026-30893 — Critical (CVSS 9.0): Wazuh is a free and open source platform used for threat prevention, detection, and response. From version 4.4.0 to…
CVE-2023-50260 — High (CVSS 8.8): Wazuh is a free and open source platform used for threat prevention, detection, and response. A wrong validation in the…

All CVEs affecting Wazuh →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.
CVE-2026-20131 — Critical (CVSS 10.0): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could…
CVE-2026-25632 — Critical (CVSS 10.0): EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water…
CVE-2025-14931 — Critical (CVSS 10.0): Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability.…

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →