CVE-2026-1199

LOWNVD 3.73.7
EchelonGraph scoreMEDIUM confidence

Score 3.7 from GitHub Security Advisory published 2026-08-18. NVD baseline CVSS 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.7
EG Score
3.7(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity37% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 18, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Aug 18, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-1199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
zabbix1:6.0.14+dfsg-1 ... 1:7.0.9+dfsg-1~bpo12+1 (28 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
zabbix1:7.0.10+dfsg-2 ... 1:7.0.29+dfsg-2 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
zabbix1:7.0.10+dfsg-2 ... 1:7.0.27+dfsg-1 (6 versions)1:7.0.29+dfsg-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 66× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 22:01 UTCEG score recompute
  2. 2026-09-20 22:01 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-17 21:53 UTCEG score recompute
  5. 2026-09-17 21:53 UTCGHSA enrichment
  6. 2026-09-16 14:07 UTCEPSS rescore
  7. 2026-09-16 05:14 UTCEPSS rescore
  8. 2026-09-14 16:30 UTCEG score recompute
  9. 2026-09-14 16:30 UTCGHSA enrichment
  10. 2026-09-13 16:46 UTCEPSS rescore
  11. 2026-09-12 15:00 UTCEPSS rescore
  12. 2026-09-11 16:20 UTCEG score recompute
  13. 2026-09-11 16:20 UTCGHSA enrichment
  14. 2026-09-11 14:52 UTCEPSS rescore
  15. 2026-09-11 09:36 UTCEPSS rescore
  16. 2026-09-10 09:34 UTCEPSS rescore
  17. 2026-09-08 22:00 UTCEPSS rescore
  18. 2026-09-08 16:12 UTCEG score recompute 3.20
  19. 2026-09-08 16:12 UTCGHSA enrichment
  20. 2026-09-08 15:27 UTCNVD updateCVSS v3 → 3.7 · severity → LOW
  21. 2026-09-08 00:38 UTCEG score recompute
  22. 2026-09-08 00:38 UTCGHSA enrichment
  23. 2026-09-07 16:01 UTCEPSS rescore
  24. 2026-09-07 00:38 UTCEG score recompute
  25. 2026-09-07 00:37 UTCGHSA enrichment
Show 54 more
  1. 2026-09-06 13:47 UTCEPSS rescore
  2. 2026-09-06 00:14 UTCEG score recompute
  3. 2026-09-06 00:14 UTCGHSA enrichment
  4. 2026-09-05 00:10 UTCEG score recompute
  5. 2026-09-05 00:10 UTCGHSA enrichment
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-03 22:36 UTCGHSA enrichment
  8. 2026-09-02 22:02 UTCEG score recompute
  9. 2026-09-02 22:01 UTCGHSA enrichment
  10. 2026-09-02 14:11 UTCEPSS rescore
  11. 2026-09-01 21:03 UTCGHSA enrichment
  12. 2026-09-01 15:13 UTCEG score recompute
  13. 2026-09-01 15:13 UTCGHSA enrichment
  14. 2026-09-01 13:53 UTCEPSS rescore
  15. 2026-09-01 04:39 UTCEPSS rescore
  16. 2026-08-31 15:11 UTCEG score recompute
  17. 2026-08-31 15:11 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 15:11 UTCEG score recompute
  20. 2026-08-30 15:11 UTCGHSA enrichment
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-29 15:09 UTCEG score recompute
  23. 2026-08-29 15:09 UTCGHSA enrichment
  24. 2026-08-28 21:41 UTCEPSS rescore
  25. 2026-08-28 15:08 UTCGHSA enrichment
  26. 2026-08-27 14:58 UTCEG score recompute
  27. 2026-08-27 14:58 UTCGHSA enrichment
  28. 2026-08-27 14:25 UTCEPSS rescore
  29. 2026-08-26 14:52 UTCEG score recompute
  30. 2026-08-26 14:52 UTCGHSA enrichment
  31. 2026-08-26 14:46 UTCEPSS rescore
  32. 2026-08-25 14:50 UTCEG score recompute
  33. 2026-08-25 14:50 UTCGHSA enrichment
  34. 2026-08-25 13:48 UTCEPSS rescore
  35. 2026-08-24 14:50 UTCEG score recompute
  36. 2026-08-24 14:49 UTCGHSA enrichment
  37. 2026-08-23 14:49 UTCEG score recompute
  38. 2026-08-23 14:49 UTCGHSA enrichment
  39. 2026-08-23 00:19 UTCEPSS rescore
  40. 2026-08-22 14:49 UTCEG score recompute
  41. 2026-08-22 14:49 UTCGHSA enrichment
  42. 2026-08-21 23:49 UTCEPSS rescore
  43. 2026-08-21 14:48 UTCEG score recompute
  44. 2026-08-21 14:48 UTCGHSA enrichment
  45. 2026-08-20 22:55 UTCEPSS rescore
  46. 2026-08-20 14:48 UTCEG score recompute
  47. 2026-08-20 14:47 UTCGHSA enrichment
  48. 2026-08-19 17:03 UTCEPSS rescore
  49. 2026-08-19 14:47 UTCGHSA enrichment
  50. 2026-08-18 14:44 UTCEG score recompute
  51. 2026-08-18 13:48 UTCEG score recompute
  52. 2026-08-18 13:22 UTCEG score recompute
  53. 2026-08-18 12:26 UTCEG score recompute
  54. 2026-08-18 12:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-1199?
CVE-2026-1199 is a low vulnerability published on August 18, 2026. 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.
When was CVE-2026-1199 disclosed?
CVE-2026-1199 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1199 actively exploited?
CVE-2026-1199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-1199?
CVE-2026-1199 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-1199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1199, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-1199

Explore →

Is Your Infrastructure Affected by CVE-2026-1199?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.