PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-45798 wazuh CVE debrief

A vulnerability in Wazuh, a free and open-source platform for threat prevention, detection, and response, allows remote denial of service. The issue, fixed in versions 4.14.6 and 5.0.0-beta2, involves improper handling of attacker-controlled version strings in the compare_wazuh_versions() function. This function copies an attacker-controlled enrollment V: field into a 10-byte stack buffer using strncpy() without explicit termination. A version string of at least nine non-null bytes can cause strchr() and strtok() to read beyond ver2 and can make strtok() write a null byte into adjacent stack memory. The vulnerability is reachable before authentication through wazuh-authd on TCP 151

Vendor
wazuh
Product
Unknown
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-19
Original CVE updated
2026-09-09
Advisory published
2026-08-19
Advisory updated
2026-09-09

Who should care

Defenders and administrators responsible for Wazuh installations, particularly those using versions between 4.5.0 and 4.14.6 or 5.0.0-beta2, should assess exposure and apply patches or compensating controls as needed.

Why it matters

CVE-2026-45798 is a vulnerability in Wazuh that allows remote denial of service. Defenders should prioritize verifying exposure and applying patches, focusing on systems using Wazuh versions between 4.5.0 and 4.14.6 or 5.0.0-beta2, especially those with anonymous TLS enrollment enabled. Evidence is limited, and additional information on potential exploitation or victim impact is not available.

  • Potential remote denial of service
  • Need to verify Wazuh version and configuration
  • Possible impact on system availability

Technical summary

The compare_wazuh_versions() function in Wazuh's src/shared/version_op.c copies an attacker-controlled enrollment V: field into a 10-byte stack buffer using strncpy() without explicit termination. A version string of at least nine non-null bytes can cause strchr() and strtok() to read beyond ver2 and can make strtok() write a null byte into adjacent stack memory, allowing a remote denial of service.

Defensive priority

Defenders should prioritize verifying exposure and applying patches, focusing on systems using Wazuh versions between 4.5.0 and 4.14.6 or 5.0.0-beta2, especially those with anonymous TLS enrollment enabled.

Recommended defensive actions

  • Verify Wazuh version and check for exposure
  • Apply patches or updates to vulnerable versions
  • Review and adjust configuration for anonymous TLS enrollment
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, additional information on potential exploitation or victim impact is limited.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-45798 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-45798

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-45798 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-45798

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.