Embedded sensitive-data retrieval via hard-coded key
Published Oct 1, 2026 · Updated Oct 1, 2026
Use of a hard-coded cryptographic key in Johnson Controls EasyIO FS32 before 3.0b63 allows attackers to retrieve embedded sensitive data. The available CVE description does not disclose where the key resides, which cryptographic operation uses it, or how the data is reached. The access required to obtain or use the key is unspecified; the reported outcome is retrieval of embedded sensitive data, not controller control.
Summary
What happened
Use of a hard-coded cryptographic key in Johnson Controls EasyIO FS32 before 3.0b63 allows attackers to retrieve embedded sensitive data. The available CVE description does not disclose where the key resides, which cryptographic operation uses it, or how the data is reached. The access required to obtain or use the key is unspecified; the reported outcome is retrieval of embedded sensitive data, not controller control.
The record
- CVE
- CVE-2026-71449
- Published
- Oct 1, 2026
- Updated
- Oct 1, 2026
- Vendor
- Johnson Controls
- Product
- EasyIO FS32
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 1, 2026CVE publishedPublication date reported by the CVE source.
- Oct 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.0b63
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started