# CVE-2025-62790: Wazuh vulnerable to NULL pointer dereference in fim_fetch_attributes_state

> A compromised agent can crash the Wazuh manager's analysisd service by sending a crafted message, causing denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 29 Oct 2025
- **Also known as:** GHSA-9xj3-vc52-48p9

## What is CVE-2025-62790?

CVE-2025-62790 is a medium-severity vulnerability in Wazuh Wazuh, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wazuh is a free and open source platform used for threat prevention, detection, and response. Prior to 4.11.0, fim_fetch_attributes_state() implementation does not check whether time_string is NULL or not before calling strlen() on it. A compromised agent can cause a crash of analysisd by sending a specially crafted message to the wazuh manager. An attacker who is able to craft and send an agent message to the wazuh manager can cause analysisd to crash and make it unavailable. This vulnerability is fixed in 4.11.0.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-252 (Unchecked Return Value)

## Which versions are affected by CVE-2025-62790?

It affects 1 product.


Products: Wazuh Wazuh.

## How do I fix CVE-2025-62790?

No fix has been published for CVE-2025-62790 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62790 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62790 exists.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62790 and fix it if it is affected.

What it is: CVE-2025-62790 is a medium-severity vulnerability in Wazuh Wazuh, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62790 exists.

Affected product: Wazuh Wazuh. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62790/ (Markdown: https://insights.sbomify.com/CVE-2025-62790/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62790
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62790
- OSV: https://osv.dev/vulnerability/CVE-2025-62790

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62790/
Summaries are generated and may contain mistakes; the official description above is the record.