{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32876 exists.","fix":"No fix has been published for CVE-2025-32876 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32876 is a medium-severity vulnerability in n/a, published on 20 Jun 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-32876 and fix it if it is affected.\n\nWhat it is: CVE-2025-32876 is a medium-severity vulnerability in n/a, published on 20 Jun 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-32876 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-32876/ (Markdown: https://insights.sbomify.com/CVE-2025-32876/index.md)","id":"CVE-2025-32876","markdown":"https://insights.sbomify.com/CVE-2025-32876/index.md","name":"CVE-2025-32876","record":{"aliases":["GHSA-rvp9-hfhr-8ggg"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"COROS smartwatch","requires_auth":"none","summary":"Attackers within Bluetooth range can eavesdrop on COROS PACE 3 smartwatch communications due to weak BLE Legacy Pairing with a zero Temporary Key.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"coros_pace_3_firmware","vendor":"yftech"}],"cvss":{"score":6.8,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An issue was discovered on COROS PACE 3 devices through 3.0808.0. The BLE implementation of the COROS smartwatch does not support LE Secure Connections and instead enforces BLE Legacy Pairing. In BLE Legacy Pairing, the Short-Term Key (STK) can be easily guessed. This requires knowledge of the Temporary Key (TK), which, in the case of the COROS Pace 3, is set to 0 due to the Just Works pairing method. An attacker within Bluetooth range can therefore perform sniffing attacks, allowing eavesdropping on the communication.","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":"Weak cryptography in n/a","id":"CVE-2025-32876","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2025-32877"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2025-32875"},"products":["n/a"],"published":"2025-06-20","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2025-32877","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2025-32878","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2025-32880","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":9.1,"headline":"Denial of service in n/a","id":"CVE-2025-48706","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2025-32879","kev_date_added":null,"published":"2025-06-20"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2025-48705","kev_date_added":null,"published":"2025-06-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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-06-24","vendors":["n/a"]},"summary":"Attackers within Bluetooth range can eavesdrop on COROS PACE 3 smartwatch communications due to weak BLE Legacy Pairing with a zero Temporary Key.","url":"https://insights.sbomify.com/CVE-2025-32876/"}