CVE-2025-56800 json
Reolink desktop application 8.18.12 contains a vulnerability in its local authentication mechanism.
published 2025-10-21 12 mo ago modified 2026-11-05 3 d ago also EUVD-2025-35227
- cvss
- 5.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12 mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- shinycolumn.notion.site https://shinycolumn.notion.site/reolink-auth-bypass referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/shinyColumn/CVE-2025-56800 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 5.1 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
References
-
shinycolumn.notion.site
/reolink-auth-bypass
exploit, third-party-advisory
-
github.com
/shinyColumn/CVE-2025-56800
exploit, third-party-advisory
Sources
- CVE List CVE-2025-56800
- NVD CVE-2025-56800
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.