Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessApproach lock within Bluetooth range
-
DeliveryObserve/intercept BLE pairing traffic
-
ExploitAbuse weak IV / protocol misuse (CWE-1204)
-
ExecutionForge valid lock command
-
ImpactBypass authentication and unlock door
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Attacker must be within Bluetooth (BLE) radio proximity of a SwitchBot Door Lock Series device and interact with its wireless communication protocol; the flaw (CWE-1204, weak initialization vector / cryptographic misuse) lets the attacker bypass the lock's authentication without any valid credential, PIN, or app pairing (PR:N, UI:N), affecting default deployments of the lock, keypad, and companion app. Limiting factors: exploitation is non-remote and does not scale - it requires per-target physical proximity within BLE range (~10 m) and the ability to interact with/observe the lock's live Bluetooth traffic, so it is suited to targeted physical intrusion rather than widespread attack. |
| Impact | This is a genuine physical-security risk but narrower in reach than the 8.5 score alone suggests. The input CVSS 4.0 vector specifies AV:L (local) with AC:L/PR:N/UI:N, meaning no authentication and no user interaction, but because the attack targets Bluetooth communication the realistic vector is adjacent/proximity-based - an attacker must be within BLE radio range (roughly 10 m) of the target lock. The vulnerable-system impact is significant (VI:H/VA:H, integrity and availability of the lock's access-control state) with subsequent-system impact (SI:H/SA:H) reflecting compromise of the physical door/premises the lock protects. No EPSS score, no CISA KEV listing, and no explicit POC flag were provided, so there is no public exploit identified at time of analysis; however, a detailed vendor-independent advisory and technical blog from neodyme are referenced, which typically lower the bar to practical exploitation even without packaged exploit code. Net: a real, targeted physical-intrusion priority for owners of affected SwitchBot locks, but not a mass/remote/internet-exploitable issue - exploitation does not scale and requires an attacker physically near each target. Note the AV:L designation is debatable: Bluetooth normally maps to AV:A (adjacent); verify intended attack range with the vendor/researcher. |
| Exploit ScenarioDerived | An attacker positions themselves within Bluetooth range of a SwitchBot Door Lock and manipulates the BLE communication protocol, abusing the weak/misused cryptographic handshake (CWE-1204) to bypass the lock's authentication and access controls. With no credentials or user interaction required (PR:N/UI:N), the attacker sends crafted protocol messages that cause the lock to open. A public technical advisory and blog describe the flaw, but no standalone proof-of-concept exploit tool is flagged in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Bluetooth authentication bypass in SwitchBot Door Lock Series allows an attacker within BLE range to manipulate the lock's communication protocol and bypass electronic lock and access controls without valid credentials, a PIN, or app pairing (PR:N, UI:N). The root cause is CWE-1204 cryptographic misuse, specifically weak initialization vector or related BLE protocol weaknesses, and exploitation is non-remote and does not scale because it requires per-target physical proximity within roughly 10 meters and interaction with live Bluetooth traffic. No public exploit identified at time of analysis; the risk is a targeted physical-intrusion issue that is narrower in reach than the 8.5 score alone suggests.
RemediationAI
No vendor-released patch is identified in the provided data; monitor https://neodyme.io/en/advisories/cve-2026-8374/ for vendor guidance and apply firmware or app updates as soon as they are released. Until a fix is confirmed, reduce exposure by restricting physical proximity to the lock, avoiding placement in publicly reachable areas where an attacker can linger within BLE range, and adding mechanical or secondary physical security controls that do not depend solely on the electronic lock; this adds operational burden and does not fix the underlying BLE cryptographic misuse. If the product configuration allows it, disable or restrict Bluetooth-based remote unlock or keypad pairing features when not needed, understanding that this can break app control and legitimate keypad use. Audit access logs and unexpected lock state changes, and treat PIN secrecy as insufficient protection because the bypass does not require valid credentials; continue to check https://neodyme.io/en/blog/switchbot/ for updated technical mitigations.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SwitchBot Door Lock Series devices use Bluetooth Low Energy for communication among the lock, keypad, and companion app, as reflected by the CPE entries for switchbot:lock_series_lock, switchbot:lock_series_keypad, and switchbot:lock_series_app. The root-cause class is CWE-1204, weak initialization vector or cryptographic misuse, meaning the BLE protocol's cryptographic protection can be bypassed rather than defeated by credential theft or conventional remote exploitation. The independent assessment maps the issue to CVSS 3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H, consistent with a nearby unauthenticated attacker who can interact with or observe live Bluetooth traffic and then bypass access controls or manipulate lock state; the original CVSS 4.0 score of 8.5 reflects high integrity and availability impact, while the assessed vector highlights that the attack remains proximity-bound and does not scale remotely.
Know when Bluetooth gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H/S:P/AU:N/R:I/V:D/RE:H/U:Red
Bluetooth proximity makes it AV:A not AV:L; protocol flaw needs no credentials (PR:N); unlocking the physical door is I:H/A:H with scope change (S:C) since the lock compromise affects the protected premises.
Primary rating from Vendor (cirosec).
CVSS VectorVendor: cirosec
DescriptionCVE.org
Misuse and misconfiguration in Bluetooth communication in SwitchBot Door Lock Series allows an attacker to bypass the electronic lock and access controls via a manipulated communication protocol.
Executive ViewAI
SwitchBot Door Lock Series contains a high-severity Bluetooth authentication bypass that can allow an attacker within approximately 10 meters to open or manipulate affected locks without credentials, directly undermining physical access controls in facilities that rely on these devices. Because no vendor-released patch is available, organizations with sensitive, regulated, or high-security physical spaces face a targeted intrusion risk that is limited by proximity but still material. Leadership should treat this as an operational physical-security exposure requiring immediate inventory and compensating controls.
No vendor-released patch identified at time of analysis. Interim mitigations include removing or isolating affected locks from sensitive areas, adding physical secondary locks or manned verification, monitoring Bluetooth/BLE activity near locks, restricting physical access to devices, and planning replacement with an alternative access-control product; apply vendor patch once released.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unauthenticated Bluetooth Low Energy OTA firmware upgrade in the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware
CVE-2025-32879 is a security vulnerability (CVSS 8.8) that allows an attacker. Risk factors: public PoC available.
Zephyr's Bluetooth Low Energy connection-response handler fails to verify that a connection request was actually initiat
Heap OOB write in Android Bluetooth driver via incorrect bounds check.
A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an att
Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may
Memory corruption in the Zephyr RTOS LE Audio Broadcast Sink (subsys/bluetooth/audio/bap_broadcast_sink.c) lets an attac
A memory leak combined with a use-after-free in the Linux kernel's Bluetooth HCI connection-setup path can crash the ker
A race condition in the Linux kernel's Bluetooth L2CAP subsystem allows a use-after-free of the hci_conn::l2cap_data poi
Out-of-bounds read in the Linux kernel Bluetooth subsystem's eir_get_service_data() leaks kernel heap memory into usersp
Use-after-free in the Linux kernel Bluetooth L2CAP stack lets a Bluetooth-adjacent attacker corrupt kernel memory by rac
Kernel crashes with a NULL-pointer dereference in the Linux kernel's Bluetooth L2CAP socket layer when l2cap_sock_cleanu
EUVD-2026-95745
GHSA-33hw-v5j3-gx3r
NVD
CVE.org
EPSS
Exploit-DB