Skip to main content

Fire-Boltt BSW013 EUVDEUVD-2026-97893

| CVE-2026-109570 MEDIUM
Missing Authentication for Critical Function (CWE-306)
2026-10-12 disclosure@vulncheck.com GHSA-hf79-56cq-w4qp
5.3
CVSS 4.0 · Vendor: vulncheck
View

Attack ChainAIDerived

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

  1. Access
    Approach target within Bluetooth range
  2. Delivery
    Connect to BLE command characteristic unpaired
  3. Exploit
    Compute CRC-16/ARC checksum for command
  4. Execution
    Write spoofed notification payload
  5. Impact
    Watch vibrates and displays phishing alert

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to be within Bluetooth Low Energy radio range of the target BSW013 watch (AV:A - physical proximity, typically a few meters, not remote/internet-based). No pairing, authentication, or user interaction is needed (PR:N/UI:N), and the only integrity protection on the proprietary command characteristic is a CRC-16/ARC checksum, which is an error-detection code with no cryptographic security and is trivially recomputed by an attacker. Limiting factors: the attack targets one device at a time, requires physical proximity (cannot be conducted at scale or over the internet), and impact is confined to spoofed notification display and vibration (phishing/social-engineering) - it cannot read device data or cause denial of service.

Impact

This is a genuine but low-severity, narrow-impact issue rather than a high-priority emergency. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N) confirms the attack is adjacent (Bluetooth range only - NOT network-reachable), low-complexity, and requires no authentication or user interaction, consistent with the CWE-306 missing-authentication root cause and the 'unpaired attackers' language in the description. However, impact is deliberately scoped low: only VI:L (integrity) is set, with confidentiality (VC:N) and availability (VA:N) untouched - the attacker can spoof notification text and vibrate the watch, but cannot read data or disrupt the device, which is why the score lands at 5.3 (Medium). No EPSS score, SSVC decision, or KEV status was supplied in the input, so automatability and exploitation-in-the-wild signals cannot be evaluated. A public research/exploit repository is referenced (github.com/Pratham-16/fireboltt-Bsw013-BLE-vuln), indicating exploit code likely exists, but this is POC availability and must not be conflated with active exploitation. Net: the adjacency requirement (physical Bluetooth proximity, one target at a time) and phishing-only impact cap real-world risk far below what the 'unauthenticated/no-UI' metrics might suggest in isolation.

Exploit ScenarioDerived

An attacker within Bluetooth range of a victim's Fire-Boltt BSW013 watch (e.g., in a cafe, transit, or office) writes a crafted command to the proprietary BLE command characteristic without pairing, protected only by a trivially-computable CRC-16/ARC checksum. The watch vibrates and displays attacker-chosen alert text - for example a fake bank or delivery notification - to socially engineer the victim into a phishing action. Public research/exploit code appears to exist in the referenced GitHub repository, lowering the effort to reproduce.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 12, 2026

Notification injection in Fire-Boltt BSW013 smartwatches (firmware through V0.0.8) allows unpaired attackers within Bluetooth Low Energy range to send spoofed alerts and vibrate the device, enabling phishing via fake notifications. The vulnerability stems from missing authentication on a proprietary BLE command characteristic, with only a non-cryptographic CRC-16 checksum protecting commands. No public exploit code has been identified at the time of analysis, and the impact is limited to integrity (spoofed notifications) without confidentiality or availability loss.

RemediationAI

No vendor-released patch has been identified at the time of analysis. Users should monitor Fire-Boltt for firmware updates beyond V0.0.8 and apply them when available. As a compensating control, disable Bluetooth on the smartwatch when not in use to eliminate the attack vector; however, this disables all notification and companion app functionality. Additionally, avoid displaying sensitive information in notifications and be cautious of unexpected alerts, as the attack only spoofs notifications and does not compromise data. There is no way to restrict BLE access to trusted devices because the vulnerable characteristic lacks authentication, so physical proximity awareness is the only other mitigation, which is not a reliable technical control.

Affected VersionsENISA

BSW013 0 ≤V0.0.8

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is classified as CWE-306: Missing Authentication for Critical Function. The Fire-Boltt BSW013 smartwatch exposes a proprietary Bluetooth Low Energy (BLE) command characteristic that accepts write operations without any pairing or authentication checks. Attackers within radio range can send crafted BLE packets that include a valid CRC-16/ARC checksum-a simple error-detection code that provides no cryptographic protection and can be easily recomputed-to trigger vibration and display arbitrary notification text. The affected firmware versions are through V0.0.8. This design flaw allows spoofed notifications but does not permit reading device data, executing code, or causing denial of service.

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 (vulncheck) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
vuln.today AI 4.3 MEDIUM

Adjacent BLE access (AV:A), no pairing/auth or interaction (PR:N/UI:N), low-complexity write; impact limited to spoofed notifications so I:L only, with no confidentiality or availability effect.

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

Primary rating from Vendor (vulncheck).

CVSS VectorVendor: vulncheck

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

DescriptionCVE.org

Fire-Boltt BSW013 smartwatch firmware through V0.0.8 contains a missing authentication vulnerability that allows unpaired attackers to inject notifications by writing to the proprietary BLE command characteristic. Attackers within Bluetooth range can craft commands protected only by a CRC-16/ARC checksum to vibrate the watch and display spoofed alert text for phishing.

Threat Intelligence Overview

EPSS Score
0.2%
Top 94% exploitable
Prevalence
Low
consumer smartwatch model, no enterprise/production footprint
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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
Scheduled
Exploitation
Poc
System Exposure· derived
Controlled
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
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-8374 HIGH
8.5 Oct 09

Bluetooth authentication bypass in SwitchBot Door Lock Series allows an attacker within BLE range to manipulate the lock

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

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