How severe is CVE-2025-56800?

CVE-2025-56800 has a CVSS 3.x base score of 5.1, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.

Is CVE-2025-56800 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-56800?

CVE-2025-56800 affects Reolink. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-56800?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2025-56800 have an EU (EUVD) identifier?

Yes. CVE-2025-56800 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-35227.

When was CVE-2025-56800 published?

CVE-2025-56800 was published on 2025-10-21 and last updated on 2026-06-17.

CVE-2025-56800

CVE-2025-56800 is a medium-severity vulnerability in Reolink with a CVSS 3.x base score of 5.1. 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-290.

Key facts

Severity: Medium (CVSS 3.x base score 5.1)
EPSS exploit prediction: 0% (15th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-35227
Weakness: CWE-290
Affected product: Reolink
Published: 2025-10-21
Last modified: 2026-06-17

Description

Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication. NOTE: this is disputed by the Supplier because the lock-screen bypass would only occur if the local user modified his own instance of the application.

Frequently asked questions

What is CVE-2025-56800?: Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism. The application implements lock screen password logic entirely on the client side using JavaScript within an Electron resource file. Because the password is stored and returned via a modifiable JavaScript property(a.settingsManager.lockScreenPassword), an attacker can patch the return value to bypass authentication. NOTE: this is disputed by the Supplier because the lock-screen bypass would only occur if the local user modified his own instance of the application.
How severe is CVE-2025-56800?: CVE-2025-56800 has a CVSS 3.x base score of 5.1, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability none.
Is CVE-2025-56800 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-56800?: CVE-2025-56800 affects Reolink. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-56800?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2025-56800 have an EU (EUVD) identifier?: Yes. CVE-2025-56800 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-35227.
When was CVE-2025-56800 published?: CVE-2025-56800 was published on 2025-10-21 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:reolink:reolink:8.18.12:*:*:*:desktop:*:*:*

More vulnerabilities in Reolink

CVE-2025-55619 — Critical (CVSS 9.8): Reolink v4.54.0.4.20250526 was discovered to contain a hardcoded encryption key and initialization vector. An attacker…
CVE-2025-56799 — Medium (CVSS 6.5): Reolink desktop application 8.18.12 contains a command injection vulnerability in its scheduled cache-clearing…
CVE-2025-55622 — Medium (CVSS 6.5): Reolink v4.54.0.4.20250526 was discovered to contain a task hijacking vulnerability due to inappropriate taskAffinity…
CVE-2025-55621 — Medium (CVSS 6.5): An Insecure Direct Object Reference (IDOR) vulnerability in Reolink v4.54.0.4.20250526 allows unauthorized attackers to…
CVE-2025-55625 — Medium (CVSS 6.3): An open redirect vulnerability in Reolink v4.54.0.4.20250526 allows attackers to redirect users to a malicious site via…
CVE-2025-55620 — Medium (CVSS 6.1): A cross-site scripting (XSS) vulnerability in the valuateJavascript() function of Reolink v4.54.0.4.20250526 allows…

All CVEs affecting Reolink →

Other CWE-290 vulnerabilities

CVE-2026-54782 — Critical (CVSS 10.0): CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1,…
CVE-2026-48567 — Critical (CVSS 10.0): Authentication bypass by spoofing in Azure HorizonDB allows an unauthorized attacker to elevate privileges over a…
CVE-2026-6213 — Critical (CVSS 10.0): A vulnerability in Remote Spark SparkView before build 1122 allows an attacker to bypasses the local connection check…
CVE-2026-39858 — Critical (CVSS 10.0): Traefik is an HTTP reverse proxy and load balancer. Prior to versions 2.11.43, 3.6.14, and 3.7.0-rc.2, there is a high…
CVE-2025-66570 — Critical (CVSS 10.0): cpp-httplib is a C++11 single-file header-only cross platform HTTP/HTTPS library. Prior to 0.27.0, a vulnerability…
CVE-2025-34063 — Critical (CVSS 10.0): A cryptographic authentication bypass vulnerability exists in OneLogin AD Connector prior to 6.1.5 due to the exposure…

Browse all CWE-290 vulnerabilities →