Threats / Wazuh / CVE-2025-24016
CVE-2025-24016
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Wazuh Server vulnerability
Wazuh Server contains a deserialization of untrusted data vulnerability enabling remote code execution. The flaw is actively exploited in the wild.
Verdict
Today item — known-exploited.
An unauthenticated or low-privileged attacker can exploit unsafe deserialization in Wazuh Server to achieve remote code execution with server privileges. Active exploitation in the wild elevates risk despite no ransomware attribution.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
54 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-06-10).
Probability (EPSS)
EPSS 0.92579 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Wazuh, Wazuh Server. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-502 Deserialization of Untrusted Data — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious serialized object and send it to the Wazuh Server deserialization endpoint.
Business
Attacker gains arbitrary code execution within the security monitoring infrastructure.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute commands as the Wazuh Server process user to establish persistence and lateral movement.
Business
Entire security monitoring capability is compromised, disabling threat detection and incident response.
3
Lateral reach — past segmentation narrative 3
Attacker
I access or exfiltrate security logs, agent communications, and configuration data stored on the server.
Business
Sensitive security telemetry and infrastructure details are exposed to adversaries.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05