{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56800 exists.","fix":"No fix has been published for CVE-2025-56800 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56800 is a medium-severity authentication bypass vulnerability in n/a, published on 21 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56800 and fix it if it is affected.\n\nWhat it is: CVE-2025-56800 is a medium-severity authentication bypass vulnerability in n/a, published on 21 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56800 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-56800/ (Markdown: https://insights.sbomify.com/CVE-2025-56800/index.md)","id":"CVE-2025-56800","markdown":"https://insights.sbomify.com/CVE-2025-56800/index.md","name":"CVE-2025-56800","record":{"aliases":["GHSA-6wpr-v4mr-q5hf"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Reolink desktop application","requires_auth":"none","summary":"Attackers can bypass the local lock screen by modifying client-side JavaScript, though the vendor disputes this as requiring local user modification.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"reolink","vendor":"reolink"}],"cvss":{"score":5.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-10-18","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-10-18T15:18:04Z","kind":"github_poc","ref":"https://github.com/shinyColumn/CVE-2025-56800","stars":0,"title":"Local Authentication Bypass Vulnerability in Reolink Desktop Application"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-56800","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2025-56801"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-56799"},"products":["n/a"],"published":"2025-10-21","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2025-55619","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.5,"headline":"Command injection in n/a","id":"CVE-2025-56799","kev_date_added":null,"published":"2025-10-21"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2025-55621","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2025-55622","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.3,"headline":"Open redirect in n/a","id":"CVE-2025-55625","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-55620","kev_date_added":null,"published":"2025-08-22"},{"cvss_score":5.4,"headline":"Auth bypass in n/a","id":"CVE-2025-55623","kev_date_added":null,"published":"2025-08-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-22","vendors":["n/a"]},"summary":"Attackers can bypass the local lock screen by modifying client-side JavaScript, though the vendor disputes this as requiring local user modification.","url":"https://insights.sbomify.com/CVE-2025-56800/"}