CVE-2026-49441
Wazuh cluster path-traversal allows remote code execution via crafted archive.
Is CVE-2026-49441 being exploited?
Not confirmed. CVE-2026-49441 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.52% probability of exploitation in the next 30 days.
How severe is CVE-2026-49441?
CVE-2026-49441 is rated Critical. 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-49441?
Yes. A fix has been recorded for CVE-2026-49441. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49441 affect?
CVE-2026-49441 affects Wazuh Manager (clustered) 4.3.0 - 4.14.5, Wazuh 5.0.0-beta prior to 5.0.0-beta3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49441?
Upgrade to 4.14.6 or 5.0.0-beta3; rotate Fernet keys and restrict cluster peer access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A cluster peer with the shared Fernet key can overwrite files (e.g., /var/ossec/etc/ossec.conf) and trigger root command execution after service reload.
Immediate action required
- affected>= 4.3.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.