Local cryptanalytic attack via hard-coded key
Published Aug 14, 2026 · Updated Aug 14, 2026
Hard-coded key use in Johnson Controls Airwall before 4.1 allows local users to defeat cryptographic protection via a cryptanalytic attack. Johnson Controls has not disclosed where the key is embedded, which data or cryptographic operation uses it, or whether the key is shared across installations. Local access is required, but the published record does not identify the files, credentials, or other protected material exposed by the attack.
Summary
What happened
Hard-coded key use in Johnson Controls Airwall before 4.1 allows local users to defeat cryptographic protection via a cryptanalytic attack. Johnson Controls has not disclosed where the key is embedded, which data or cryptographic operation uses it, or whether the key is shared across installations. Local access is required, but the published record does not identify the files, credentials, or other protected material exposed by the attack.
The record
- CVE
- CVE-2026-64887
- Published
- Aug 14, 2026
- Updated
- Aug 14, 2026
- Vendor
- Johnson Controls
- Product
- Airwall
- Classifications
- CWE-321, CAPEC-112
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 14, 2026CVE publishedPublication date reported by the CVE source.
- Aug 14, 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 <4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo