CVE-2026-32983
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWazuh 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Wazuh Manager authd service through version 4.7.3 fails to properly restrict client-initiated SSL/TLS renegotiation. Remote attackers can exploit this by sending excessive renegotiation requests, causing excessive CPU consumption and rendering the authd service unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 4.7.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Wazuh Manager versionRun 'wazuh-control info' or check '/var/ossec/' for version file, or query the API endpoint /manager/versionAffected if Version is 4.7.3 or lower (any version <= 4.7.3 is affected)
-
Verify authd service is runningRun 'wazuh-control status' or check if process 'wazuh-authd' is active, or check port 1515 is listeningAffected if Authd service is exposed and accepting connections on the network
-
Check SSL/TLS renegotiation configurationInspect authd configuration in /var/ossec/etc/authd.yml or /var/ossec/etc/ossec.conf for ssl section, look for renegotiation settingsAffected if Client-initiated SSL/TLS renegotiation is not explicitly disabled or limited
-
Confirm network exposure of authdCheck /var/ossec/etc/ossec.conf for <auth> section, verify if <use_password> or <certificates> are configured and if the service binds to external interfacesAffected if Authd is reachable from untrusted networks without additional protections
A user is affected if they run Wazuh Manager version 4.7.3 or lower with the authd service exposed and SSL/TLS renegotiation is not explicitly restricted in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement SSL/TLS renegotiation limits in the authd service configuration, or upgrade to a patched version when available. Consider rate-limiting incoming connections at the network level as an interim control.
- Consultation3.0 h
- Implementation5.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32983 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data