Summary
CVE-2026-71449 is a critical vulnerability affecting the Johnson Controls EasyIO FS32 building automation controller. The flaw stems from a hard-coded cryptographic key embedded in the device firmware, which allows an unauthenticated, remote attacker to retrieve embedded sensitive data over the network. The issue is rated CRITICAL with a CVSS v4.0 base score of 10.0, reflecting its network-exploitable nature, lack of required privileges or user interaction, and high impact to confidentiality, integrity, and availability.
Technical details
- Root cause: EasyIO FS32 firmware ships with a cryptographic key hard-coded into the device (CWE-321: Use of Hard-coded Cryptographic Key), rather than generating or provisioning a unique key per device.
- Trigger conditions: No special configuration is required; any device running affected firmware contains the same embedded key by design.
- Attack vector: Network (AV:N) — exploitable remotely with low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and no attack requirements beyond network access (AT:N).
- Impact: Because the key is static and shared across devices, disclosure or extraction of the key from one unit (e.g., via firmware extraction or protocol interaction) can allow an attacker to decrypt protected data, forge or tamper with encrypted communications, or otherwise undermine cryptographic protections relied upon by the controller — resulting in high impact to confidentiality, integrity, and availability (VC:H/VI:H/VA:H/SC:H/SI:H/SA:H).
Affected software
- Johnson Controls EasyIO FS32 — all firmware versions before 3.0b63
Severity
- CVSS v4.0 Base Score: 10.0 (Critical)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Mitigation and recommended actions
- Immediate: Upgrade all EasyIO FS32 controllers to firmware version 3.0b63 or later, which resolves this hard-coded key issue.
- If immediate patching is not possible:
- Ensure EasyIO FS32 controllers are not directly exposed to the internet; restrict access to trusted management networks only.
- Place affected devices behind a firewall or VPN and limit network access to authorized engineering workstations.
- Monitor building automation network segments for unexpected or anomalous access to FS32 controllers.
- Treat any cryptographic material or credentials tied to affected firmware as potentially compromised, and rotate any dependent secrets after upgrading.

