CVE-2026-5434: Improper storage of sensitive information
Honeywell Control
Network Module (CNM) contains
insertion of sensitive information into an unintended directory. An attacker could exploit this vulnerability through probing
system files, potentially resulting in unintended
access to protected data.
Honeywell
recommends updating to the most recent version of this product, service or
offering [200.1]. The CNM versions affected are from [100.1, 101.1, 110.1, and 110.2].
Security readout for executives and security teams
Plain-English summary
Honeywell Control Network Module may place sensitive information in an unintended directory. An unauthenticated attacker could probe system files and potentially access protected data. The issue affects confidentiality rather than system integrity or availability. Honeywell recommends upgrading affected installations to version 200.1.
Executive priority
Prioritize remediation in the normal vulnerability cycle, accelerating systems reachable from untrusted or broadly accessible networks. Although rated medium, successful exploitation may disclose sensitive protected data. Confirm inventory promptly because the source bundle contains inconsistent affected-version formatting.
Technical view
CVE-2026-5434 is a CWE-538 information-exposure flaw in Honeywell CNM. Its CVSS 3.1 score is 5.9: network-accessible, unauthenticated, and requiring no user interaction, but with high attack complexity. Successful exploitation could cause high confidentiality impact without documented integrity or availability impact.
Likely exposure
The narrative identifies CNM versions 100.1, 101.1, 110.1, and 110.2 as affected. Exposure depends on whether attackers can reach the relevant service and probe accessible system files. The bundle does not describe deployment prevalence, exposed interfaces, or the specific protected data at risk.
Exploitation context
The bundle provides no evidence of public exploitation, exploit code, or inclusion in CISA KEV; KEV is explicitly false. Exploitation is characterized as unauthenticated and network-based, but high complexity. The exact prerequisites and file locations are not disclosed.
Researcher notes
The description lists versions 100.1, 101.1, 110.1, and 110.2, while the structured affected entry explicitly contains only 100.1 and defaults other versions to unaffected. Treat the narrative list as the stated affected scope pending Honeywell clarification. No specific directory, data type, detection indicator, or exploit prerequisite is supplied.
Mitigation direction
Inventory Honeywell CNM installations and identify versions 100.1, 101.1, 110.1, or 110.2.
Update affected CNM installations to version 200.1, following Honeywell product-security guidance.
Restrict network access to CNM services while upgrades are planned and completed.
Review Honeywell advisories for deployment-specific precautions or revised remediation guidance.
Validation and detection
Confirm each CNM installation's deployed version using approved asset-management or administrative records.
Verify affected systems successfully report version 200.1 after updating.
Review access controls to ensure CNM services are reachable only by authorized networks and administrators.
Inspect relevant monitoring records for unexplained probing or access to protected system files.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-538: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-538 · source CWE mapping
Insertion of Sensitive Information into Externally-Accessible File or Directory
Insertion of Sensitive Information into Externally-Accessible File or Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.