# CVE-2026-109570: Fire-Boltt BSW013 through V0.0.8 Unauthenticated BLE Notification Injection

> Unpaired attackers within Bluetooth range can inject spoofed notifications and trigger vibrations on Fire-Boltt BSW013 smartwatches due to missing authentication on BLE commands.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-hf79-56cq-w4qp

## What is CVE-2026-109570?

CVE-2026-109570 is a medium-severity missing authorization vulnerability in Fire-Boltt BSW013, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-109570?


## How do I fix CVE-2026-109570?

No fix has been published for CVE-2026-109570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-109570 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109570 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-109570 and fix it if it is affected.

What it is: CVE-2026-109570 is a medium-severity missing authorization vulnerability in Fire-Boltt BSW013, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109570 exists.

Affected product: Fire-Boltt BSW013. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-109570/ (Markdown: https://insights.sbomify.com/CVE-2026-109570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-109570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-109570
- OSV: https://osv.dev/vulnerability/CVE-2026-109570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-109570/
Summaries are generated and may contain mistakes; the official description above is the record.