NewsCompaniesFlawsGuides
Get the app

CVE-2025-24016

From Exploited flaws, HARD’s guide to the flaws being used in attacks · Checked
This article is about a flaw in Wazuh Server. For every flaw being used in attacks, see Exploited flaws.

CVE-2025-24016 is a security flaw in Wazuh Server. Attackers can run their own code on Wazuh Server. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 10 Jun 2025.[1]

Wazuh Server is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Wazuh has published a fix or advice.

Description

CISA calls it a server deserialization of untrusted data in Wazuh Wazuh Server. In its words: “Wazuh contains a deserialization of untrusted data vulnerability that allows for remote code execution on Wazuh servers.”[1]

The CVE record adds: “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.”[2]

The underlying weakness is deserialization of untrusted data (CWE-502), in MITRE’s list of common software weaknesses.

It scores 9.9 out of 10 on the Common Vulnerability Scoring System, which rates it critical, scored by the organisation that published the CVE using CVSS 3.1.[2]

Affected versions

NVD’s record doesn’t list version ranges for it; Wazuh’s advisory has them[3]. CISA names the product as Wazuh Wazuh Server.

Most families won’t have Wazuh Server; it’s for whoever looks after IT at work.

Exploitation

CISA added it to its catalog of known exploited vulnerabilities on 10 Jun 2025, 120 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 1 Jul 2025 to fix it.[1]

FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 94%. That’s in the top 1% of the flaws it scores.[4]

CISA assesses it as not automatable: each attack takes some work.

CISA doesn’t say who was attacked, or how.

Fix

Wazuh has published a fix or advice.[3] CISA’s required action: “Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.”[1]

  1. Check whether you use it.Wazuh Server is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
  2. Send this page to your IT person.Ask them to confirm it’s fixed, or not in use. CISA gave US government agencies until 1 Jul 2025 to fix it.
  3. If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.

You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.

Timeline

DateEvent
The flaw is made public in the National Vulnerability Database, with a severity score of 9.9.[2]
CISA adds it to its catalog of flaws known to be used in attacks.[1]
CISA’s deadline for US government agencies to fix it.[1]
FIRST puts the odds of it being used in attacks in the next 30 days at 94%.[4]

See also

Other deserialization of untrusted data flaws

  • CVE-2021-23758, Ajax.NET Professional: deserialization of untrusted data ·
  • CVE-2026-63077, JetBrains TeamCity: deserialization of untrusted data ·
  • CVE-2026-50522, Microsoft SharePoint: deserialization of untrusted data ·
  • CVE-2026-58644, Microsoft SharePoint: deserialization of untrusted data ·
  • CVE-2026-45659, Microsoft SharePoint Server: deserialization of untrusted data ·

Added the same day

  • CVE-2025-33053, Microsoft Windows: external control of file name or path ·

References

  1. ^ Cybersecurity and Infrastructure Security Agency. “Wazuh Server Deserialization of Untrusted Data Vulnerability”. Known Exploited Vulnerabilities Catalog, added 10 Jun 2025.
  2. ^ National Institute of Standards and Technology. “CVE-2025-24016 Detail”. National Vulnerability Database, published 10 Feb 2025.
  3. ^ Wazuh. Advisories and fixes: wazuh.com, github.com.
  4. ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.938, percentile 99.8, 31 Oct 2026.
  5. CVE Program. “CVE-2025-24016”. The official CVE record.

This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.