CVE-2025-55619

CVE-2025-55619 is a critical-severity vulnerability in Reolink with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-321.

Key facts

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.

Frequently asked questions

What is CVE-2025-55619?
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.
How severe is CVE-2025-55619?
CVE-2025-55619 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-55619 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (30th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-55619?
CVE-2025-55619 affects Reolink. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-55619?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-55619 have an EU (EUVD) identifier?
Yes. CVE-2025-55619 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-25610.
When was CVE-2025-55619 published?
CVE-2025-55619 was published on 2025-08-22 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Reolink

All CVEs affecting Reolink →

Other CWE-321 vulnerabilities

Browse all CWE-321 vulnerabilities →