# CVE-2026-74036: Wazuh 4.3.0 before 4.14.8 Remote Code Execution via SCA Command Policies

> Attackers controlling the manager can execute arbitrary commands as root on agents by exploiting improper trust validation of SCA policy files.

- **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-qmhg-366r-jjfp

## What is CVE-2026-74036?

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

### Official description

Wazuh from 4.3.0 before 4.14.8 contains a remote code execution vulnerability where SCA policy trust is determined by file path rather than configuration source. Attackers controlling a manager can write unsigned policy files to var/incoming via the upgrade channel and reference them to execute command checks as root on agents.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-74036 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-74036 is a high-severity missing authorization vulnerability in wazuh-agent, 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-74036 exists.

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

## Sources

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

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