# CVE-2026-74041: Wazuh 4.14.3 < 4.14.8 / 4.10.4 Remote Command Validation Bypass via Case Mismatch

> Authenticated users can bypass command validation to execute arbitrary commands as root on Wazuh managers.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-cjf8-wjx6-hjw6

## What is CVE-2026-74041?

CVE-2026-74041 is a high-severity vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Wazuh 4.14.3 before 4.14.8 and 4.10.4 contains a case-sensitivity mismatch between the ossec.conf validator and wazuh-logcollector that bypasses remote-command validation. Authenticated users with manager:update_config can inject an uppercase LOG_FORMAT command localfile that the collector runs as root on reload.

Weakness: CWE-178 (Improper Handling of Case Sensitivity)

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


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

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

## Is CVE-2026-74041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74041 is a high-severity vulnerability in wazuh-manager, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-74041 exists.

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

## Sources

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

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