Quick answers
- Is CVE-2026-1199 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-1199 being exploited in the wild.
- How severe is CVE-2026-1199?
- Low severity, with a CVSS score of 3.7, published 18 August 2026.
- Which products and versions are affected?
- Zabbix 6.0.0 - 6.0.46, 7.0.0 - 7.0.27, 7.4.0 - 7.4.11.
- Is there a fix for CVE-2026-1199?
- A patch was published on 2026-08-18: Fixed in versions 6.0.47, 7.0.28, and 7.4.12 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-1199 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-1199?
- Check whether you run Zabbix at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a race condition vulnerability in the login lockout mechanism affecting Zabbix's API and Frontend components. The flaw occurs because unsuccessful login requests sent in parallel are not properly counted towards the brute-force block counter, allowing an attacker to exceed the intended threshold of failed attempts. An attacker with network access to the Zabbix Frontend or API can exploit this by sending concurrent login requests with different passwords. The vulnerability enables more password guesses than intended, significantly increasing the feasibility of brute-force attacks. Patches are available in versions 6.0.47, 7.0.28, and 7.4.12.
Affected products
- Zabbix Zabbix 6.0.0 - 6.0.46, 7.0.0 - 7.0.27, 7.4.0 - 7.4.11
Timeline
- 2026-08-18: disclosed
- 2026-08-18: patched: Fixed in versions 6.0.47, 7.0.28, and 7.4.12