CVE-2026-64894Johnson Controls EasyIO Neo IOManager and Tools Installer inclusion of untrusted functionality
CVE-2026-64894 is a inclusion of untrusted functionality in Johnson Controls EasyIO Neo IOManager and Tools Installer, rated high (7.3 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Deferred
What it is
The product loads code from a source outside its control.
How it is reached
An attacker can exploit it with physical access to the device, with an ordinary user account, but someone has to act first, such as opening a file or following a link. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run their code inside your build or your running service. The damage can spread past the vulnerable component into others.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place Johnson Controls EasyIO Neo IOManager and Tools Installer runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
Inclusion of functionality from untrusted control sphere vulnerability in Johnson Controls EasyIO Neo IOManager and Tools Installer allows Malicious Software Update.
This issue affects EasyIO Neo IOManager and Tools Installer: 1.1.0.0.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Build pipelines, dependencies and plugins. The flaw sits between third-party code and your build or runtime.
- Update channels. The flaw sits between third-party code and your build or runtime.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between third-party code and your build or runtime. An attacker who crosses it can run their code inside your build or your running service.
Questions to answer about your own systems
- Where does Johnson Controls EasyIO Neo IOManager and Tools Installer run in your systems, and at which version?
- Which of those devices sit where outsiders can touch them?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.