TLS traffic decryption via default private keys
Published Apr 27, 2026 · Updated Apr 28, 2026
Hard-coded keys in affected Milesight AIOT camera firmware allow remote attackers to decrypt protected TLS traffic. The firmware deploys SSL certificates whose private keys are identical default values rather than device-unique secrets. Exploitation requires access to captured or intercepted traffic; the shared key defeats the confidentiality and authenticity expected from TLS.
Summary
What happened
Hard-coded keys in affected Milesight AIOT camera firmware allow remote attackers to decrypt protected TLS traffic. The firmware deploys SSL certificates whose private keys are identical default values rather than device-unique secrets. Exploitation requires access to captured or intercepted traffic; the shared key defeats the confidentiality and authenticity expected from TLS.
The record
- CVE
- CVE-2026-32644
- Published
- Apr 27, 2026
- Updated
- Apr 28, 2026
- Vendor
- Milesight
- Product
- MS-Cxx61-xxxPE
- Classifications
- CWE-321, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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 <=61.8.0.5-r2
What conditions does exploitation require?
What is affected?
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