Quick answers
- Is CVE-2026-74036 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74036 being exploited in the wild.
- How severe is CVE-2026-74036?
- High severity, with a CVSS score of 7.2, published 13 October 2026.
- Which products and versions are affected?
- Wazuh Agent 4.3.0 before 4.14.8.
- Is there a fix for CVE-2026-74036?
- Yes: fixed in 4.14.8. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74036 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-74036?
- Check whether you run Wazuh Agent at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.14.8
Technical details
The vulnerability stems from insufficient path validation in SCA (Security Configuration Assessment) policy handling. The gate that enforces sca.remote_commands determines whether a policy is "remote" (untrusted) based solely on file path location rather than configuration source; a policy outside etc/shared/ is trusted. An attacker can write unsigned policy files to var/incoming/ via the upgrade channel (which performs signature checks only later), then reference them from agent.conf, causing command checks to execute as root on the agent without signature verification.
Affected products
- Wazuh Agent 4.3.0 before 4.14.8
Timeline
- 2026-10-13: disclosed
- 2026-09-25: patched