CVE-2025-24016 — AI Deep Analysis Summary

Q: Who is affected? (Versions/Components)

📦 **Affected**: Wazuh versions **4.4.0 to 4.9.1** (specifically `wazuh-manager`). ✅ **Fixed**: Versions **>= 4.9.1** are patched. 🌐 **Component**: DistributedAPI module.

Q: Is there a public Exp? (PoC/Wild Exploitation)

🔥 **Public Exp?**: **YES**. 📂 **PoCs**: Multiple GitHub repos (e.g., `huseyinstif`, `MuhammadWaseem29`, `celsius026`). 🔍 **Scanners**: Nuclei templates available for detection.

Q: How to self-check? (Features/Scanning)

🔍 **Self-Check**: Use **Nuclei** with the specific CVE-2025-24016 template. 📋 **Verify**: Check if your `wazuh-manager` version is `< 4.9.1`. 👀 **Monitor**: Look for unusual deserialization errors in API logs.

Q: Is it fixed officially? (Patch/Mitigation)

🛠️ **Official Fix**: **YES**. 📥 **Action**: Upgrade Wazuh to version **4.9.1 or higher**. 📝 **Advisory**: See GitHub Security Advisory `GHSA-hcrc-79hj-m3qh`.

Q: Is it urgent? (Priority Suggestion)

🚨 **Urgency**: **CRITICAL**. ⏱️ **Priority**: **Immediate**. 📢 **Reason**: Public PoCs exist, and RCE allows total server takeover. Patch immediately if running affected versions.

Updated May 06, 2026 CVSS 9.9 · Critical

This is a summary of the AI-generated 10-question deep analysis. The full version (longer answers, follow-up Q&A, related CVEs) requires login. Read the full analysis →

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: Wazuh suffers from **Unsafe Deserialization** in its DistributedAPI. <br>💥 **Consequences**: Attackers can inject malicious objects, leading to **Remote Code Execution (RCE)**.…

Read full answer (login)

Q2Root Cause? (CWE/Flaw)

🛡️ **Root Cause**: **CWE-502** (Deserialization of Untrusted Data).…

Read full answer (login)

Q3Who is affected? (Versions/Components)

📦 **Affected**: Wazuh versions **4.4.0 to 4.9.1** (specifically `wazuh-manager`). <br>✅ **Fixed**: Versions **>= 4.9.1** are patched. <br>🌐 **Component**: DistributedAPI module.

Q4What can hackers do? (Privileges/Data)

💀 **Hackers' Power**: Full **Remote Code Execution**. <br>🔓 **Privileges**: Can execute arbitrary Python code on the server.…

Read full answer (login)

Q5Is exploitation threshold high? (Auth/Config)

⚠️ **Threshold**: **Medium**. <br>🔑 **Requirement**: Attacker needs **API Access** (e.g., compromised dashboard, cluster node, or misconfigured agent). <br>🚫 **No Auth?…

Read full answer (login)

Q6Is there a public Exp? (PoC/Wild Exploitation)

🔥 **Public Exp?**: **YES**. <br>📂 **PoCs**: Multiple GitHub repos (e.g., `huseyinstif`, `MuhammadWaseem29`, `celsius026`). <br>🔍 **Scanners**: Nuclei templates available for detection.

Q7How to self-check? (Features/Scanning)

🔍 **Self-Check**: Use **Nuclei** with the specific CVE-2025-24016 template. <br>📋 **Verify**: Check if your `wazuh-manager` version is `< 4.9.1`. <br>👀 **Monitor**: Look for unusual deserialization errors in API logs.

Q8Is it fixed officially? (Patch/Mitigation)

🛠️ **Official Fix**: **YES**. <br>📥 **Action**: Upgrade Wazuh to version **4.9.1 or higher**. <br>📝 **Advisory**: See GitHub Security Advisory `GHSA-hcrc-79hj-m3qh`.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: Restrict API access strictly. <br>🔒 **Network**: Block external access to the Wazuh API port.…

Read full answer (login)

Q10Is it urgent? (Priority Suggestion)

🚨 **Urgency**: **CRITICAL**. <br>⏱️ **Priority**: **Immediate**. <br>📢 **Reason**: Public PoCs exist, and RCE allows total server takeover. Patch immediately if running affected versions.

Continue exploring

Vulnerability detail Full AI analysis (login) wazuh CWE-502