CVE-2026-48024
Wazuh cluster path traversal lets peers overwrite ossec.conf and achieve root code execution
Is CVE-2026-48024 being exploited?
Not confirmed. CVE-2026-48024 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-48024?
CVE-2026-48024 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48024?
Yes. A fix has been recorded for CVE-2026-48024. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48024 affect?
CVE-2026-48024 affects Wazuh Manager, Wazuh framework, Wazuh cluster (versions 4.0.0–4.14.5; pre-fix 5.0 beta). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48024?
Upgrade to 4.14.6+ or 5.0.0-beta3+, rotate Fernet keys, audit/restore ossec.conf and restrict cluster peers
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote root code execution: a cluster peer with the shared Fernet key can use path traversal in merged archives to overwrite ossec.conf and execute commands as root.
Immediate action required
- affected>= 4.0.0 and < 4.14.6
- affected>= 5.0.0-beta1 and < 5.0.0-beta3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.