{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55623 exists.","fix":"No fix has been published for CVE-2025-55623 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55623 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55623 and fix it if it is affected.\n\nWhat it is: CVE-2025-55623 is a medium-severity authentication bypass vulnerability in n/a, published on 22 Aug 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55623 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-55623/ (Markdown: https://insights.sbomify.com/CVE-2025-55623/index.md)","id":"CVE-2025-55623","markdown":"https://insights.sbomify.com/CVE-2025-55623/index.md","name":"CVE-2025-55623","record":{"aliases":["GHSA-p374-753h-f3x5"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink mobile app","requires_auth":"none","summary":"Attackers can bypass the lock screen authentication in the Reolink mobile application by utilizing Android Debug Bridge (ADB).","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"reolink","vendor":"reolink"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"An issue in the lock screen component of Reolink v4.54.0.4.20250526 allows attackers to bypass authentication via using an ADB (Android Debug Bridge).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-55623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Open redirect in n/a","id":"CVE-2025-55624"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2025-55622"},"products":["n/a"],"published":"2025-08-22","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"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-22","vendors":["n/a"]},"summary":"Attackers can bypass the lock screen authentication in the Reolink mobile application by utilizing Android Debug Bridge (ADB).","url":"https://insights.sbomify.com/CVE-2025-55623/"}