Skip to main content

SwitchBot Door Lock CVE-2026-8374

| EUVDEUVD-2026-95745 HIGH
Generation of Weak Initialization Vector (IV) (CWE-1204)
2026-10-09 cirosec GHSA-33hw-v5j3-gx3r
8.5
CVSS 4.0 · Vendor: cirosec
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Approach lock within Bluetooth range
  2. Delivery
    Observe/intercept BLE pairing traffic
  3. Exploit
    Abuse weak IV / protocol misuse (CWE-1204)
  4. Execution
    Forge valid lock command
  5. Impact
    Bypass 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.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Lock Series Keypad 0 ≤2.7
Lock Series App 0 ≤9.2.6
Lock Series Lock 0 ≤3.4

Affected Packages

euvd lock_series_app no fix
euvd lock_series_keypad no fix
euvd lock_series_lock no fix

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

Vendor (cirosec) PRIMARY 8.5 HIGH
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
vuln.today AI 9.6 CRITICAL

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.

3.1 AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H

Primary rating from Vendor (cirosec).

CVSS VectorVendor: cirosec

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
Low
Subsequent system: Integrity
High
Subsequent system: Availability
High

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

Why It Matters

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.

Business Impact: High
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

EPSS Score
0.1%
Top 100% exploitable
Prevalence
Medium
popular consumer smart-home lock brand, limited enterprise/production footprint
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact
High

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2025-65824 HIGH POC
8.8 Dec 10

Unauthenticated Bluetooth Low Energy OTA firmware upgrade in the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware

CVE-2025-32879 HIGH POC
8.8 Jun 20

CVE-2025-32879 is a security vulnerability (CVSS 8.8) that allows an attacker. Risk factors: public PoC available.

CVE-2025-10457 HIGH POC
8.1 Sep 19

Zephyr's Bluetooth Low Energy connection-response handler fails to verify that a connection request was actually initiat

CVE-2025-20672 CRITICAL
9.8 Jun 02

Heap OOB write in Android Bluetooth driver via incorrect bounds check.

CVE-2026-55330 CRITICAL
9.8 Oct 06

A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an att

CVE-2020-10135 MEDIUM POC
5.4 May 19

Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may

CVE-2026-19570 HIGH
8.8 Oct 09

Memory corruption in the Zephyr RTOS LE Audio Broadcast Sink (subsys/bluetooth/audio/bap_broadcast_sink.c) lets an attac

CVE-2026-90255 HIGH
8.8 Sep 17

A memory leak combined with a use-after-free in the Linux kernel's Bluetooth HCI connection-setup path can crash the ker

CVE-2026-90256 HIGH
8.8 Sep 17

A race condition in the Linux kernel's Bluetooth L2CAP subsystem allows a use-after-free of the hci_conn::l2cap_data poi

CVE-2026-89583 HIGH
8.1 Sep 11

Out-of-bounds read in the Linux kernel Bluetooth subsystem's eir_get_service_data() leaks kernel heap memory into usersp

CVE-2026-90092 HIGH
8.0 Sep 17

Use-after-free in the Linux kernel Bluetooth L2CAP stack lets a Bluetooth-adjacent attacker corrupt kernel memory by rac

CVE-2026-90091 HIGH
8.0 Sep 17

Kernel crashes with a NULL-pointer dereference in the Linux kernel's Bluetooth L2CAP socket layer when l2cap_sock_cleanu

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy