CVE-2026-105624 · Vendor
NO FIX YET · SEE WHAT TO DO
Zenitel Connect before 1.11.0 locks a user account after repeated failed logins. A remote attacker who knows or guesses a username can keep triggering that lockout and deny the real user web access.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run Zenitel Connect with its web interface reachable by users or the network. The sources say Intercom call handling is not affected, so the risk is limited to web login and account lockout. unknown whether internet exposure is required.
Not affected if intercom-only-use, version-1.11.0-or-later
Who cares web-interface, zenitel-connect
unknown if the sources do not give the exact location.1.11.0.1.11.0 (the sources say versions before 1.11.0 are affected).The login flow in Zenitel Connect before 1.11.0 applies per-account lockout on repeated failed login attempts, which allows remote attackers to cause a denial of service (temporary lockout of targeted user accounts from the web interface, repeatable for as long as the attack continues) via repeated failed login requests for a known or guessed username. Intercom call handling is not affected.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.