CVE-2026-32644
Certain firmware versions of Milesight AIOT cameras ship with SSL certificates that use the same default private key. This means anyone who can discover the key can impersonate the camera or decrypt its traffic, potentially taking control or spying on its communications.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
Milesight AIOT cameras running the affected firmware versions that use default SSL private keys. Users of these cameras, such as small businesses or home security owners, are at risk.
Real-world impact
An attacker who obtains the default private key could pretend to be the camera, intercept or alter data sent to or from the camera, and potentially gain remote control or access to sensitive video streams.
Why this severity
The CVSS score of 9.2 reflects that the vulnerability is easy to exploit over the network, requires no authentication, and gives an attacker full confidentiality, integrity, and availability impact on the camera. Because the flaw is in the SSL certificate, it can be used to bypass encryption and impersonate the device, making it a critical risk.
What to do about it
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
No fix documented in sources
Timeline
- Apr 28, 2026 · Apr 28, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 25, 2026 · 11d agoAdvisory updatedThe NVD record was last revised.