# CVE-2026-109571: Fire-Boltt BSW013 firmware through V0.0.8 Unauthenticated Heart Rate Disclosure via BLE

> Unpaired Bluetooth devices can read live heart rate data from Fire-Boltt BSW013 smartwatches without authentication or user consent.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/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:** 26 Oct 2026
- **Also known as:** GHSA-hj6p-cc45-4m6g

## What is CVE-2026-109571?

CVE-2026-109571 is a low-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 BLE devices to subscribe to the Heart Rate Measurement characteristic (0x2A37). Attackers within Bluetooth range can receive the wearer's live heart rate readings without pairing, bonding, or any confirmation on the watch.

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

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


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

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

## Is CVE-2026-109571 being exploited?

There is no known exploitation of CVE-2026-109571 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109571 is a low-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: There is no known exploitation of CVE-2026-109571 in the wild and no public exploit code.

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-109571/ (Markdown: https://insights.sbomify.com/CVE-2026-109571/index.md)
```

## Sources

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

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