{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-62843 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62843 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62843 is a low-severity vulnerability in QNAP Systems Inc. QuRouter, published on 20 Mar 2026. 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-62843 and fix it if it is affected.\n\nWhat it is: CVE-2025-62843 is a low-severity vulnerability in QNAP Systems Inc. QuRouter, published on 20 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62843 in the wild and no public exploit code.\n\nAffected product: QNAP Systems Inc. QuRouter. 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-62843/ (Markdown: https://insights.sbomify.com/CVE-2025-62843/index.md)","id":"CVE-2025-62843","markdown":"https://insights.sbomify.com/CVE-2025-62843/index.md","name":"CVE-2025-62843","record":{"aliases":["GHSA-v9ww-wgw5-f4f7"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"QNAP QuRouter","requires_auth":"none","summary":"Attackers with physical access can bypass communication channel restrictions to gain unauthorized privileges on QNAP QuRouter devices.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qnap","cpe":[{"product":"qurouter","vendor":"qnap"}],"cvss":{"score":0.9,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"An improper restriction of communication channel to intended endpoints vulnerability has been reported to affect QHora. If an attacker gains physical access, they can then exploit the vulnerability to gain the privileges that were intended for the original endpoint.\n\nWe have already fixed the vulnerability in the following version:\nQuRouter 2.6.3.009 and later","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"QuRouter","id":"CVE-2025-62843","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"QuRouter","id":"CVE-2025-62844"},"packages":[],"prev":{"headline":"HBS 3 Hybrid Backup Sync","id":"CVE-2025-62842"},"products":["QuRouter"],"published":"2026-03-20","related":[{"cvss_score":9.5,"headline":"QuRouter","id":"CVE-2024-50389","kev_date_added":null,"published":"2024-12-06"},{"cvss_score":9.5,"headline":"QHora","id":"CVE-2024-48860","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":7.7,"headline":"QHora","id":"CVE-2024-50390","kev_date_added":null,"published":"2025-03-07"},{"cvss_score":7.3,"headline":"QuRouter","id":"CVE-2025-62846","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.3,"headline":"QHora","id":"CVE-2024-48861","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":7.1,"headline":"QuRouter 2.5","id":"CVE-2025-29887","kev_date_added":null,"published":"2025-08-29"},{"cvss_score":5.6,"headline":"QuRouter","id":"CVE-2025-62845","kev_date_added":null,"published":"2026-03-20"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-25","vendors":["QNAP Systems Inc."]},"summary":"Attackers with physical access can bypass communication channel restrictions to gain unauthorized privileges on QNAP QuRouter devices.","url":"https://insights.sbomify.com/CVE-2025-62843/"}