Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-55619 is a critical-severity Use of Hard-coded Cryptographic Key (CWE-321) vulnerability in Reolink Reolink. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Private Keys (T1552.004); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-55619 is a critical vulnerability in the Reolink Android application version v4.54.0.4.20250526, where a hardcoded encryption key and initialization vector (IV) are used for protecting sensitive data. Classified under CWE-321 (Use of Hard-coded Cryptographic Key), the flaw enables decryption of access tokens and web session tokens stored inside the app. It carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), reflecting its high severity due to the ease of exploitation and potential for severe impacts.
Any attacker capable of reverse engineering the Reolink app can exploit this vulnerability by extracting the hardcoded key and IV to decrypt the protected tokens. No special privileges, user interaction, or physical access are required, and the attack can originate remotely over the network with low complexity. Successful exploitation grants access to sensitive credentials, potentially allowing unauthorized account access, session hijacking, or further compromise of connected Reolink devices and services.
References point to CWE definitions for hard-coded keys (CWE-321) and insufficient entropy in PRNG (CWE-329), Android's EncryptedSharedPreferences documentation, a related vulnerability (CVE-2020-25173), and a Notion page detailing the hardcoded AES key and IV in the Reolink Android app. No specific advisories, patches, or mitigation steps are detailed in the provided information.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-25610
Vulnerability Data
Reolink v4.54.0.4.20250526 was discovered to contain a hardcoded encryption key and initialization vector. An attacker can leverage this vulnerability to decrypt access tokens and web session tokens stored inside the app via reverse engineering.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requiring cryptographic keys to be established and managed according to defined requirements prevents developers from embedding static unchangeable keys.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-SDLC activities such as code review and secret scanning directly prevent embedding static keys.
Data-at-rest protection policies require proper key management and therefore discourage hard-coded keys.
Data-in-transit protection similarly depends on non-hard-coded keys for encryption.
Configuration baselines and reviews can prohibit hard-coded keys in deployed artifacts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Key-management controls that govern generation, rotation and protection of keys make the use of embedded hard-coded cryptographic keys less likely and easier to detect.