CyberSecBulletin
CVE-2025-55619NVD status: Analyzed

Reolink: Use of Hard-coded Cryptographic Key

Published Updated By the CyberSecBulletin desk

CVE-2025-55619 is a critical-severity use of hard-coded cryptographic key vulnerability in Reolink, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Reolink versions: 4.54.0.4.20250526. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of Reolink you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ReolinkReolink4.54.0.4.20250526Not stated

Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of Hard-coded Cryptographic Key

The product uses a hard-coded, unchangeable cryptographic key.

How developers prevent this class of flaw

  • Prevention schemes mirror that of hard-coded password storage.

More Use of Hard-coded Cryptographic Key vulnerabilities (CWE-321)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Use of Hard-coded Cryptographic Key vulnerabilities

Spotted an error? Tell us.