The Reolink desktop application uses a hard-coded and predictable AES encryption key to encrypt user configuration files allowing attackers with local access to decrypt sensitive application data stored in %APPDATA%. A different vulnerability than CVE-2025-56801. NOTE: the Supplier's position is that material is not hardcoded and is instead randomly generated on each installation of the application.
References
| Link | Resource |
|---|---|
| https://github.com/shinyColumn/CVE-2025-56802 | Exploit Third Party Advisory |
| https://shinycolumn.notion.site/reolink-aes-key | Exploit Third Party Advisory |
Configurations
History
17 Nov 2025, 16:04
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Reolink
Reolink reolink |
|
| References | () https://github.com/shinyColumn/CVE-2025-56802 - Exploit, Third Party Advisory | |
| References | () https://shinycolumn.notion.site/reolink-aes-key - Exploit, Third Party Advisory | |
| CPE | cpe:2.3:a:reolink:reolink:8.18.12:*:*:*:desktop:*:*:* |
22 Oct 2025, 14:15
| Type | Values Removed | Values Added |
|---|---|---|
| Summary | (en) The Reolink desktop application uses a hard-coded and predictable AES encryption key to encrypt user configuration files allowing attackers with local access to decrypt sensitive application data stored in %APPDATA%. A different vulnerability than CVE-2025-56801. NOTE: the Supplier's position is that material is not hardcoded and is instead randomly generated on each installation of the application. |
21 Oct 2025, 21:15
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.1 |
| CWE | CWE-321 |
21 Oct 2025, 19:21
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-10-21 19:21
Updated : 2025-11-17 16:04
NVD link : CVE-2025-56802
Mitre link : CVE-2025-56802
CVE.ORG link : CVE-2025-56802
JSON object : View
Products Affected
reolink
- reolink
CWE
CWE-321
Use of Hard-coded Cryptographic Key
