{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55625 exists.","fix":"No fix has been published for CVE-2025-55625 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55625 is a medium-severity 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-55625 and fix it if it is affected.\n\nWhat it is: CVE-2025-55625 is a medium-severity 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-55625 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-55625/ (Markdown: https://insights.sbomify.com/CVE-2025-55625/index.md)","id":"CVE-2025-55625","markdown":"https://insights.sbomify.com/CVE-2025-55625/index.md","name":"CVE-2025-55625","record":{"aliases":["GHSA-5pq5-797c-c89v"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Reolink camera firmware","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via crafted URLs in Reolink firmware, though the vendor disputes this as intentional Alexa integration behavior.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"reolink","vendor":"reolink"}],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"An open redirect vulnerability in Reolink v4.54.0.4.20250526 allows attackers to redirect users to a malicious site via a crafted URL. NOTE: this is disputed by the Supplier because it is intentional behavior that supports redirection to Alexa URLs, which are not guaranteed to remain at the same domain indefinitely.","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":"Open redirect in n/a","id":"CVE-2025-55625","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing authorization in n/a","id":"CVE-2025-55626"},"packages":[],"prev":{"headline":"Open redirect in n/a","id":"CVE-2025-55624"},"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.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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-11","vendors":["n/a"]},"summary":"Attackers can redirect users to malicious sites via crafted URLs in Reolink firmware, though the vendor disputes this as intentional Alexa integration behavior.","url":"https://insights.sbomify.com/CVE-2025-55625/"}