Wazuh is a free and open source platform used for threat prevention, detection, and response. In versions 4.6.0 and above, prior to 4.14.5, a logic error in CheckRateLimitsMiddleware.dispatch() causes the /events endpoint rate check to unconditionally overwrite the general rate limit result. When the global max_request_per_minute is exceeded, requests to /events still succeed if the events-specific counter (hardcoded 30/min) has not been reached. This allows event injection into analysisd beyond the admin-configured global rate limit. This issue has been fixed in version 4.14.5.
CVE-2026-33434
This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 82% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity71% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 20, 2026
Advisory Details (1)
Auto-updated Jul 17, 2026Rate Limit Bypass via /events Endpoint · Advisory · wazuh/wazuh · GitHub
Affected: 4.9.1 via ALLOWED_CALLABLES |
https://github.com/wazuh/wazuh/security/advisories/GHSA-37qc-8242-6crgWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 22× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-26 22:50 UTCEG score recompute
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 11:23 UTCEG score recompute
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:09 UTCEG score recompute
- 2026-07-23 00:24 UTCEG score recompute▲ 2.80
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-20 03:15 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:32 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 23:59 UTCEG score recompute
- 2026-07-16 23:59 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-33434?
When was CVE-2026-33434 disclosed?
Is CVE-2026-33434 actively exploited?
What is the CVSS score of CVE-2026-33434?
How do I remediate CVE-2026-33434?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-33434
Is Your Infrastructure Affected by CVE-2026-33434?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.