Skip to content
vulnerability

CVE-2025-24016

9.9
Critical
KEV · Exploited in wildEPSS 94%Patch available

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.

exploited
Yes, in CISA KEV since 10 Jun 2025fix by 1 Jul 2025 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 93.8%
Published 10 Feb 2025Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-502· Insecure Deserialization

Can a WAF block it? Partly. Cloudflare publishes WAF a rule written for this CVE. Such rules block the known exploit requests and buy time, but attackers can change the request to get past them, so they do not replace the patch.

Also consider: patch · enable the vendor rule in block mode · allow-list classes

Based on WAF vendor rules published for this CVE. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requiredlowuser interactionnonescopechangedconfidentialitylowintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:H
common questions

Is CVE-2025-24016 being exploited?

Yes. CVE-2025-24016 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2025-24016?

CVE-2025-24016 is rated Critical with a CVSS score of 9.9. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-24016?

Yes. A fix has been recorded for CVE-2025-24016. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-24016 affect?

CVE-2025-24016 affects wazuh:wazuh. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
wazuh:wazuh
affected versions
wazuh
  • affected>= 4.4.0 and < 4.9.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 Metasploit module · 8 GitHub proofs of concept · 1 Nuclei template

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 20 Aug 2025 (SSVC 2.0.3).

timeline

  1. 10 Feb 2025Published
  2. 13 Feb 2025First public exploit or proof of concept · 2 days later
  3. 10 Jun 2025Added to CISA KEV (exploited in the wild) · 117 days (about 4 months) later
  4. 1 Jul 2025CISA remediation due date (US federal agencies) · 21 days later
  5. 20 Aug 2025CISA SSVC assessment: exploitation active · 50 days later
  6. 26 Feb 2026CVE record last updated · 191 days (about 6 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later

also known as

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
2 references in the CVE record: 2 links
  • Linkgithub.com /wazuh/wazuh/security/advisories/GHSA-hcrc-79hj-m3qh
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24016

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved