CVE-2026-32983: SSL/TLS Renegotiation DoS in Wazuh Manager authd service
Wazuh Manager authd service in wazuh-manager packages through version 4.7.3 contains an improper restriction of client-initiated SSL/TLS renegotiation vulnerability that allows remote attackers to cause a denial of service by sending excessive renegotiation requests. Attackers can exploit the lack of renegotiation limits to consume CPU resources and render the authd service unavailable.
Security readout for executives and security teams
Plain-English summary
A remote attacker could overload the Wazuh Manager authd service by abusing repeated SSL/TLS renegotiation. This can make agent enrollment or authentication unavailable, but the provided sources do not indicate data theft or system takeover.
Executive priority
Treat as a moderate availability risk for Wazuh operations. Prioritize exposed or internet-reachable managers first, because no authentication is required and disruption could affect monitoring operations.
Technical view
CVE-2026-32983 affects Wazuh Manager authd in wazuh-manager packages through 4.7.3. The service does not sufficiently restrict client-initiated SSL/TLS renegotiation, allowing unauthenticated network attackers to consume CPU and cause authd denial of service.
Likely exposure
Organizations exposing Wazuh Manager authd to untrusted networks have the clearest exposure. Internal-only deployments still face risk from compromised hosts or malicious insiders able to reach authd.
Exploitation context
The CVSS 4.0 vector is network, low complexity, no privileges, and no user interaction. The source bundle says KEV is false and provides no evidence of active exploitation.
Researcher notes
Evidence supports SSL/TLS renegotiation-driven DoS against authd, not confidentiality or integrity impact. The provided bundle does not include exploit-in-the-wild confirmation or detailed fixed-version text beyond affected-version statements.
Mitigation direction
Review the Wazuh GHSA and apply vendor-recommended updates or configuration changes.
Verify wazuh-manager is not within the affected version range.
Restrict authd network access to trusted management or enrollment sources.
Monitor authd CPU use, availability, and connection spikes.
Prepare operational workarounds for agent enrollment disruption.
Validation and detection
Inventory all Wazuh Manager nodes and record wazuh-manager versions.
Confirm whether authd is reachable from untrusted networks.
Check change records against the Wazuh vendor advisory.
Review service telemetry for CPU exhaustion or authd availability events.
Validate firewall or access-control rules around authd exposure.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-276: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-276 · source CWE mapping
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.