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.
Published: 2026-08-18
Score: 6.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability lies in Zabbix’s login lockout logic, where simultaneous failed login attempts are not properly tallied, enabling an attacker to exceed the intended guess limit. This flaw could allow an attacker to attempt more credential guesses than the lockout counter permits, potentially leading to a successful brute‑force or credential‑reuse attack. The weakness is a classic data race (CWE-362).

Affected Systems

Zabbix Web Application, directly affecting all installations that rely on the Zabbix API or UI for authentication. No specific versions are listed in the CNA data, but affected releases include any that have not been updated to the fixed versions indicated by the vendor.

Risk and Exploitability

The CVSS score of 6.9 indicates moderate severity; the absence of an EPSS value means the exploitation probability is unknown, but the risk is not negligible. The vulnerability is not included in CISA’s KEV catalog, suggesting no known widespread exploitation yet. The likely attack vector is remote, through the HTTP API or frontend, where an attacker could send many concurrent login requests to subvert the lockout mechanism. If the application is exposed to the internet, the risk escalates due to the ease of automating concurrent attempts.

Generated by OpenCVE AI on August 18, 2026 at 13:52 UTC.

Remediation

Vendor Solution

Update the affected components to their respective fixed versions.


OpenCVE Recommended Actions

  • Update Zabbix to the fixed versions released by the vendor
  • Implement additional rate‑limiting or concurrency controls to serialize authentication attempts
  • Monitor authentication logs for abnormal login patterns and enforce temporary IP blocking for repeated failures

Generated by OpenCVE AI on August 18, 2026 at 13:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 18 Aug 2026 14:30:00 +0000

Type Values Removed Values Added
First Time appeared Zabbix
Zabbix zabbix
Vendors & Products Zabbix
Zabbix zabbix

Tue, 18 Aug 2026 12:30:00 +0000

Type Values Removed Values Added
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.
Title API and Frontend login lockout race condition
Weaknesses CWE-362
References
Metrics cvssV4_0

{'score': 6.9, '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'}


cve-icon MITRE

Status: PUBLISHED

Assigner: Zabbix

Published:

Updated: 2026-08-18T13:35:41.648Z

Reserved: 2026-01-19T14:02:49.454Z

Link: CVE-2026-1199

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-18T13:17:20.900

Modified: 2026-09-01T20:56:59.203

Link: CVE-2026-1199

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-18T14:15:07Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')