Cyber Resilience

CVE-2025-55622

Reolink 4.54.0.4.20250526

Public PoC
Published
22 August 2025
Modified
17 June 2026
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
EPSS Score 0.0034 27th percentile
Risk Priority 50 floored blend · peak EPSS

Summary

CVE-2025-55622 is a medium-severity Object Hijack (CWE-491) vulnerability in Reolink Reolink. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 27th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Reolink v4.54.0.4.20250526 was discovered to contain a task hijacking vulnerability due to inappropriate taskAffinity settings. NOTE: this is disputed by the Supplier because it is intentional behavior to ensure a predictable user experience.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-56799Same product: Reolink Reolink
CVE-2025-56801Same product: Reolink Reolink
CVE-2025-55619Same product: Reolink Reolink
CVE-2025-55624Same product: Reolink Reolink
CVE-2025-56802Same product: Reolink Reolink
CVE-2025-55623Same product: Reolink Reolink
CVE-2025-55621Same product: Reolink Reolink
CVE-2025-55625Same product: Reolink Reolink
CVE-2025-56800Same product: Reolink Reolink
CVE-2025-55620Same product: Reolink Reolink

Affected Assets

reolink
reolink
4.54.0.4.20250526

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and code analysis can locate public non-final clone methods before deployment.

Documented development standards can mandate secure cloning patterns and final declarations.

Engineering principles can require encapsulation and final methods to block unauthorized object creation paths.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce final clone methods and constructor invariants to block object hijacking.

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.

prevents

Secure coding standards directly require final clone or defensive-copy patterns to block object hijacking.

finds

Security testing can detect clone-related state corruption during acceptance testing.

prevents

Secure development lifecycle includes design and code reviews that can catch non-final clone methods.

prevents

Application security requirements can mandate defensive coding rules that prevent unsafe cloning.

prevents

Secure architecture principles discourage mutable state exposure via cloneable objects.

References