Authorization bypass via weak key generation
Published Apr 27, 2026 · Updated Apr 27, 2026
Weak key generation in Milesight AIoT camera firmware allows attackers to bypass authorization via adjacent-network access and user interaction. CISA and Milesight have not disclosed the key-generation routine, the user-controlled key, or how the generated value is accepted. Exploitation requires proximity to the target network, high complexity, and active user interaction; successful bypass exposes device confidentiality, integrity, and availability.
Summary
What happened
Weak key generation in Milesight AIoT camera firmware allows attackers to bypass authorization via adjacent-network access and user interaction. CISA and Milesight have not disclosed the key-generation routine, the user-controlled key, or how the generated value is accepted. Exploitation requires proximity to the target network, high complexity, and active user interaction; successful bypass exposes device confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-28747
- Published
- Apr 27, 2026
- Updated
- Apr 27, 2026
- Vendor
- Milesight
- Product
- MS-Cxx61-xxxPE
- Classifications
- CWE-639
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 27, 2026CVE publishedPublication date reported by the CVE source.
- Apr 27, 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.
Weakness, pattern, technique
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