{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69969 exists.","fix":"No fix has been published for CVE-2025-69969 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69969 is a critical missing authorization vulnerability in n/a, published on 4 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-69969 and fix it if it is affected.\n\nWhat it is: CVE-2025-69969 is a critical missing authorization vulnerability in n/a, published on 4 Mar 2026. 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-69969 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-69969/ (Markdown: https://insights.sbomify.com/CVE-2025-69969/index.md)","id":"CVE-2025-69969","markdown":"https://insights.sbomify.com/CVE-2025-69969/index.md","name":"CVE-2025-69969","record":{"aliases":[],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BLE smart device","requires_auth":"none","summary":"Attackers can execute arbitrary commands and intercept data on Pebble Prism Ultra devices via unauthenticated Bluetooth Low Energy connections.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pebble_prism_ultra_firmware","vendor":"pebblepower"}],"cvss":{"score":9.6,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"A lack of authentication and authorization mechanisms in the Bluetooth Low Energy (BLE) communication protocol of SRK Powertech Pvt Ltd Pebble Prism Ultra v2.9.2 allows attackers to reverse engineer the protocol and execute arbitrary commands on the device without establishing a connection. This is exploitable over Bluetooth Low Energy (BLE) proximity (Adjacent), requiring no physical contact with the device. Furthermore, the vulnerability is not limited to arbitrary commands but includes cleartext data interception and unauthenticated firmware hijacking via OTA services.","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":"Missing authorization in n/a","id":"CVE-2025-69969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"FUXA contains an insecure default configuration vulnerability","id":"CVE-2025-69970"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-69949"},"products":["n/a"],"published":"2026-03-04","related":[],"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":"2026-03-04","vendors":["n/a"]},"summary":"Attackers can execute arbitrary commands and intercept data on Pebble Prism Ultra devices via unauthenticated Bluetooth Low Energy connections.","url":"https://insights.sbomify.com/CVE-2025-69969/"}