Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71449 – Hard-coded Cryptographic Key Exposure – Johnson Controls EasyIO FS32 (before 3.0b63

Be the first to know when new zero-days emerge:

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.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge