Security readout for executives and security teams
Plain-English summary
A Wazuh rate limiting bug lets authenticated users send /events requests even after the administrator's global per-minute request cap is exceeded, until the endpoint's separate 30/minute counter is hit. The documented impact is limited availability degradation through extra event injection, not data theft or privilege escalation. Wazuh fixed this in 4.14.5.
Executive priority
Treat this as a routine but timely security update for Wazuh environments. It is not supported by the sources as actively exploited or high-impact, but it can weaken operational controls that protect event ingestion and analysis capacity.
Technical view
In Wazuh versions 4.6.0 through before 4.14.5, CheckRateLimitsMiddleware.dispatch() mishandles /events checks by overwriting the general rate-limit result. When max_request_per_minute is exceeded, /events requests can still pass if the endpoint-specific hardcoded 30/minute limit remains available, allowing event injection into analysisd beyond the configured global limit.
Likely exposure
Exposure is limited to Wazuh deployments running versions >=4.6.0 and <4.14.5 where authenticated users can reach the API /events endpoint. The CVSS vector requires network access and low privileges, with no user interaction. Systems already upgraded to 4.14.5 are described as fixed.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The issue is a rate limit bypass affecting availability only, with CVSS 4.3 medium severity. It could matter operationally where Wazuh event ingestion capacity or alert fidelity is sensitive to excess injected events.
Researcher notes
Key evidence comes from the CVE record and Wazuh GitHub advisory. The public description identifies CWE-799, affected range, fixed version, and middleware logic flaw. No exploit details, proof of concept, or broader affected products are provided in the supplied bundle.
Mitigation direction
- Upgrade Wazuh to version 4.14.5 or later.
- Restrict Wazuh API access to trusted users and networks.
- Review Wazuh's security advisory for deployment-specific guidance.
- Monitor /events traffic for unusual authenticated request volume.
- Review global rate limit assumptions after upgrading.
Validation and detection
- Inventory Wazuh versions across managers and API nodes.
- Confirm affected systems are not running versions >=4.6.0 and <4.14.5.
- Verify Wazuh 4.14.5 or later is deployed after remediation.
- Review API logs for elevated /events request rates.
- Check whether low-privilege accounts can access /events unnecessarily.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-799: 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.
Open ATT&CK lookupCVE-2026-33434 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L2.81.4GitHub_MVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wazuh/wazuh/security/advisories/GHSA-37qc-8242-6crgCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Interaction Frequency
Improper Control of Interaction Frequency represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.