CVE-2024-36469: Zabbix · Timing Side Channel
Affects ZabbixSource GCVE Database
Not known to be exploited · CVSS 2.3 Low.
Data as of 30 Oct 2026, 00:04 UTC
Thin evidence
One scorer or none| CNA (Zabbix) | CVSS 4.0 | 2.3 |
|---|
CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Zabbix Zabbix | Affected
| Fixed in– |
AI-suggested
Users should monitor vendor advisories for updates. Given the low severity and nature of the issue, no urgent action is required. Mitigation may involve implementing consistent response times for login failures to prevent timing analysis if feasible.
Description
CVE-2024-36469 is a timing discrepancy vulnerability in Zabbix where the execution time for an unsuccessful login differs depending on whether the username exists or not. This observable timing difference could potentially allow an attacker to infer valid usernames. The vulnerability affects specific versions of Zabbix: 5.0.0, 6.0.0, 7.0.0, and 7.2.0. The CVSS 4.0 score is low, indicating limited impact and difficulty of exploitation. No known exploits are reported in the wild, and no patch information is provided.