Skip to main content
Public proof of conceptFix available

CVE-2026-25769

A public proof of concept exists; no exploitation attested.

  • Published2026-03-17
  • Fixed in4.14.3
  • WeaknessCWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2026-03-1718:16CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-25 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-25769?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-25769?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Wazuh
BranchAffectedFixed in
4.x≥ 4.0.0, < 4.14.34.14.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Wazuh to 4.14.3

Advisories and patches

Detection

read 2026-10-25 00:28 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
4 repositories, unverifiedhakaioffsec/CVE-2026-25769Samres27/CVE-2026-25769---CVE-2026-25770njeru-codes/CVE-2026-257690xBlackash/CVE-2026-25769
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-03-17
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.19.1read 2026-10-23
  • CNAweakness (CWE)CWE-502read 2026-10-23
  • FIRST EPSSEPSS score8.9 %2026-10-25
  • PoC-in-GitHubproof of concept4read 2026-10-25

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Published
2026-03-17
Last Modified
2026-06-17
NVD status
Analyzed

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.

Is CVE-2026-25769 actively exploited?

A proof-of-concept exploit exists for CVE-2026-25769, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-25769?

CVE-2026-25769 has a CVSS v3 base score of 9.1 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database