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

> Attackers can bypass login lockout mechanisms by sending simultaneous requests, allowing unlimited password guessing attempts against Zabbix accounts.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** DEBIAN-CVE-2026-1199, GHSA-vm66-478p-4mqw, UBUNTU-CVE-2026-1199

## What is CVE-2026-1199?

CVE-2026-1199 is a medium-severity vulnerability in Zabbix Zabbix, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-1199?

It affects 1 product.


Products: Zabbix Zabbix.

## How do I fix CVE-2026-1199?

Apply the vendor's patch.

## Is CVE-2026-1199 being exploited?

There is no known exploitation of CVE-2026-1199 in the wild and no public exploit code.

## Other vulnerabilities in Zabbix Zabbix

- [CVE-2022-23131](https://insights.sbomify.com/CVE-2022-23131/): Zabbix Frontend Authentication Bypass (critical 9.1, exploited in the wild)
- [CVE-2007-0640](https://insights.sbomify.com/CVE-2007-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-42327](https://insights.sbomify.com/CVE-2024-42327/): SQL injection in user.get API (critical 9.9)
- [CVE-2024-22116](https://insights.sbomify.com/CVE-2024-22116/): Remote code execution within ping script (critical 9.9)
- [CVE-2013-3738](https://insights.sbomify.com/CVE-2013-3738/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-1199 and fix it if it is affected.

What it is: CVE-2026-1199 is a medium-severity vulnerability in Zabbix Zabbix, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1199 in the wild and no public exploit code.

Affected product: Zabbix Zabbix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-1199/ (Markdown: https://insights.sbomify.com/CVE-2026-1199/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-1199
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1199
- OSV: https://osv.dev/vulnerability/CVE-2026-1199

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-1199/
Summaries are generated and may contain mistakes; the official description above is the record.