CVE-2026-3611
Honeywell Iq412 Firmware authentication bypass
- Published12 Mar 2026
Description
The Honeywell IQ4x building management controller, exposes its full web-based HMI without authentication in its factory-default configuration. With no user module configured, security is disabled by design and the system operates under a System Guest (level 100) context, granting read/write privileges to any party able to reach the HTTP interface. Authentication controls are only enforced after a web user is created via U.htm, which dynamically enables the user module. Because this function is accessible prior to authentication, a remote user can create a new account with administrative read/write permissions enabling the user module and imposing authentication under attacker-controlled credentials. This action can effectively lock legitimate operators out of local and web-based configuration and administration.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-3611 being actively exploited?
CVE-2026-3611 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.99%.
How severe is CVE-2026-3611?
CVE-2026-3611 has a CVSS 3.1 base score of 10.0, rated critical. EPSS estimates a 0.99% probability of exploitation.
Which products are affected by CVE-2026-3611?
Affected products include Honeywell Iq412 Firmware, Honeywell Iq41x Firmware, Honeywell Iq422 Firmware, Honeywell Iq4e Firmware, Honeywell Iq4nc Firmware.
How do I fix CVE-2026-3611?
Upgrade affected software to a fixed version, for example Honeywell Iq412 Firmware 3.30, Honeywell Iq41x Firmware 3.30, Honeywell Iq422 Firmware 3.30 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-3611 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.