dbcve.org
ReolinkApplication

CVE-2025-55619

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Reolink mobile application v4.54.0.4.20250526 contains a hardcoded encryption key and initialization vector (IV) embedded in the app binary. An attacker who obtains the app through reverse engineering can extract these cryptographic secrets and use them to decrypt sensitive access tokens and web session tokens stored locally by the application, enabling session hijacking and unauthorized account access.

MitigationRemove hardcoded encryption keys from the application code and implement proper key management using platform-specific secure storage mechanisms (Android Keystore or iOS Keychain) with per-instance or per-installation key generation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ReolinkApplication
Affected:= 4.54.0.4.20250526

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Reolink app is installed
    Check your device's installed applications list to confirm the Reolink mobile app is present
    Affected if The Reolink app is installed on the device
  2. Identify installed app version
    Open your device's app management settings (Android: Settings > Apps > Reolink, iOS: Settings > General > iPhone Storage) and locate the version number field
    Affected if Unable to retrieve version information from the app
  3. Compare version to affected release
    Compare the installed version number to 4.54.0.4.20250526 - verify if they match exactly
    Affected if The installed version equals exactly 4.54.0.4.20250526

If the installed Reolink mobile app version is exactly 4.54.0.4.20250526, the hardcoded cryptographic key vulnerability is present in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove hardcoded encryption keys from the application code and implement proper key management using platform-specific secure storage mechanisms (Android Keystore or iOS Keychain) with per-instance or per-installation key generation.

Fix this in Reolink Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA5.0 h
41.0 hours of engineering $7,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-55619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-55619 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data