CVE-2025-24016

CRITICALNVD 9.99.9—
EchelonGraph scoreHIGH confidence

Score elevated to 9.9 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2025-06-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.9 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Trending — 3 sources updated this weekExploited in the wild
9.9
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 94%CVSS: 9.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.9.1, an unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. DistributedAPI parameters are a serialized as JSON and deserialized using as_wazuh_object (in framework/wazuh/core/cluster/common.py). If an attacker manages to inject an unsanitized dictionary in DAPI request/response, they can forge an unhandled exception (__unhandled_exc__) to evaluate arbitrary python code. The vulnerability can be triggered by anybody with API access (compromised dashboard or Wazuh servers in the cluster) or, in certain configurations, even by a compromised agent. Version 4.9.1 contains a fix.

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
85(Attend)
EG Risk 85/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
99.8%
KEV
⚠ Exploited

Published

February 10, 2025

Last Modified

October 24, 2025

Advisory Details (2)

Auto-updated Jul 20, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24016
github Patch Available🟡 PoC Available

Remote code execution in Wazuh server · Advisory · wazuh/wazuh · GitHub

https://github.com/wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/wazuh/wazuh—4.9.1+incompatible—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:51 UTCEG score recompute
  2. 2026-07-23 00:26 UTCEG score recompute
  3. 2026-07-22 19:40 UTCCISA KEV update
  4. 2026-07-22 16:06 UTCEG score recompute
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-22 14:07 UTCEPSS rescore
  7. 2026-07-21 14:37 UTCCISA KEV update
  8. 2026-07-20 18:23 UTCEG score recompute
  9. 2026-07-20 17:07 UTCEPSS rescore
  10. 2026-07-17 07:37 UTCEG score recompute
  11. 2026-07-16 17:04 UTCCISA KEV update
  12. 2026-07-15 16:49 UTCCISA KEV update
  13. 2026-07-15 15:04 UTCCISA KEV update
  14. 2026-07-14 18:05 UTCCISA KEV update
  15. 2026-07-13 22:29 UTCEPSS rescore
  16. 2026-07-13 22:29 UTCEPSS rescore
  17. 2026-07-13 17:07 UTCCISA KEV update
  18. 2026-07-10 17:52 UTCCISA KEV update
  19. 2026-07-09 19:09 UTCEPSS rescore
  20. 2026-07-07 19:01 UTCCISA KEV update
  21. 2026-07-07 17:16 UTCCISA KEV update
  22. 2026-07-01 19:16 UTCCISA KEV update
  23. 2026-06-29 19:12 UTCCISA KEV update
  24. 2026-06-25 19:15 UTCCISA KEV update
  25. 2026-06-23 21:32 UTCEPSS rescore
Show 30 more
  1. 2026-06-23 21:32 UTCEPSS rescore
  2. 2026-06-23 17:44 UTCCISA KEV update
  3. 2026-06-18 16:13 UTCCISA KEV update
  4. 2026-06-16 19:33 UTCCISA KEV update
  5. 2026-06-16 17:52 UTCEPSS rescore
  6. 2026-06-16 17:52 UTCEPSS rescore
  7. 2026-06-15 19:33 UTCCISA KEV update
  8. 2026-06-15 17:48 UTCEPSS rescore
  9. 2026-06-12 17:35 UTCCISA KEV update
  10. 2026-06-11 19:10 UTCCISA KEV update
  11. 2026-06-10 13:22 UTCEPSS rescore
  12. 2026-06-09 18:42 UTCCISA KEV update
  13. 2026-06-09 17:12 UTCCISA KEV update
  14. 2026-06-08 19:16 UTCCISA KEV update
  15. 2026-06-08 17:26 UTCCISA KEV update
  16. 2026-06-06 13:47 UTCEPSS rescore
  17. 2026-06-06 13:47 UTCEPSS rescore
  18. 2026-06-05 22:46 UTCEPSS rescore
  19. 2026-06-05 22:46 UTCEPSS rescore
  20. 2026-06-05 22:43 UTCCISA KEV update
  21. 2026-06-03 19:09 UTCCISA KEV update
  22. 2026-06-02 20:12 UTCEPSS rescore
  23. 2026-06-02 20:12 UTCEPSS rescore
  24. 2026-06-02 18:32 UTCCISA KEV update
  25. 2026-06-01 20:42 UTCCISA KEV update
  26. 2026-05-31 22:30 UTCEPSS rescore
  27. 2026-05-31 22:30 UTCEPSS rescore
  28. 2026-05-29 22:25 UTCEG score recompute
  29. 2026-05-29 22:20 UTCCISA KEV update
  30. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(8 references)

Working exploit code is in the public domain (1 Metasploit module) (6 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCguinea-offensive-security/Wazuh-RCE
    First seen Jul 13, 2025

    Wazuh 8.4 CVE-2025-24016

    Open source ↗
  • GitHub PoCrxerium/CVE-2025-24016
    First seen Jun 10, 2025

    Detection for CVE-2025-24016 - Deserialization of Untrusted Data Vulnerability in the Wazuh software

    Open source ↗
  • GitHub PoCcybersecplayground/CVE-2025-24016-Wazuh-Remote-Code-Execution-RCE-PoC
    First seen Apr 21, 2025

    A critical RCE vulnerability has been identified in the Wazuh server due to unsafe deserialization in the wazuh-manager package. This bug affects Wazuh versions ≥ 4.4.0 and has been patched in version 4.9.1.

    Open source ↗
  • GitHub PoCMuhammadWaseem29/CVE-2025-24016
    First seen Feb 20, 2025

    CVE-2025-24016: RCE in Wazuh server! Remote Code Execution

    Open source ↗
  • GitHub PoC0xjessie21/CVE-2025-24016
    First seen Feb 16, 2025

    CVE-2025-24016: Wazuh Unsafe Deserialization Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoChuseyinstif/CVE-2025-24016-Nuclei-Template
    First seen Feb 13, 2025
    Open source ↗
  • Metasploitexploit/linux/http/wazuh_auth_rce_cve_2025_24016✓ verified
    First seen Feb 10, 2025

    Wazuh server remote code execution caused by an unsafe deserialization vulnerability.

    Open source ↗
  • Nucleihttp/cves/2025/CVE-2025-24016.yaml
    First seen Jan 1, 2025

    Wazuh - Unsafe Deserialization Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2025-24016?
CVE-2025-24016 is a critical vulnerability published on February 10, 2025. Wazuh is a free and open source platform used for threat prevention, detection, and response. Starting in version 4.4.0 and prior to version 4.9.1, an unsafe deserialization vulnerability allows for remote code execution on Wazuh servers. DistributedAPI parameters are a serialized as JSON and…
When was CVE-2025-24016 disclosed?
CVE-2025-24016 was first published in the National Vulnerability Database on February 10, 2025, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-24016 actively exploited?
Yes. CISA added CVE-2025-24016 to the Known Exploited Vulnerabilities catalog on June 10, 2025, affecting Wazuh Wazuh Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2025-24016?
CVE-2025-24016 has a CVSS v3 base score of 9.9 (NVD).
Which products are affected by CVE-2025-24016?
CVE-2025-24016 affects Wazuh Wazuh Server. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2025-24016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-24016, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-24016

Explore →

Is Your Infrastructure Affected by CVE-2025-24016?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs