# CVE-2026-61811: Wazuh: Unbounded Recursion in os_xml `_getattributes()` Causes analysisd Worker Thread Stack Exhaustion

> An attacker can cause a denial of service in Wazuh analysisd by sending crafted XML with excessive attributes, exhausting stack memory.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-9wv5-7qwx-m9w5

## What is CVE-2026-61811?

CVE-2026-61811 is a medium-severity denial of service vulnerability in wazuh, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wazuh is an open-source security platform providing unified XDR and SIEM protection for endpoints and cloud workloads. From 3.8.0 until 4.14.7, the _getattributes() function in src/os_xml/os_xml.c recursively processes every XML attribute without a depth limit while allocating two large local buffers in each stack frame. An enrolled agent can submit a Windows EventChannel event containing an element with enough attributes to exhaust the analysisd worker-thread stack, trigger a segmentation fault, and interrupt log ingestion. The element-depth limit in _ReadElem() does not constrain the number of attributes on one element, so it does not prevent this condition. This issue is fixed in version 4.14.7.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-61811?


## How do I fix CVE-2026-61811?

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

## Is CVE-2026-61811 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61811 and fix it if it is affected.

What it is: CVE-2026-61811 is a medium-severity denial of service vulnerability in wazuh, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61811 exists.

Affected product: 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-2026-61811/ (Markdown: https://insights.sbomify.com/CVE-2026-61811/index.md)
```

## Sources

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

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