CVE-2026-37271
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFire-Boltt Smartwatch FB BGS001 Firmware: MOY-JS14-2.0.4 is vulnerable to Improper Authentication, The device accepts GATT Write Request commands without sufficient authentication or strong session validation. Under specific conditions, previously captured BLE packets can be replayed from a nearby device to trigger functionality on the smartwatch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Fire-Boltt Smartwatch FB BGS001 firmware MOY-JS14-2.0.4 accepts BLE GATT Write Request commands without sufficient authentication or strong session validation. Attackers can capture and replay BLE packets from a nearby device to trigger unauthorized functionality on the smartwatch, due to missing replay attack protections and weak session management in the BLE GATT implementation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionConnect to the Fire-Boltt Smartwatch FB BGS001 via Bluetooth and read the device information service (DIS) or check the watch settings under About > Version to confirm the firmware is MOY-JS14-2.0.4Affected if The device is a Fire-Boltt FB BGS001 running firmware version MOY-JS14-2.0.4
-
Enumerate BLE GATT servicesUse a BLE debugging tool (such as nRF Connect, BLE Scanner, or gatttool) to discover all GATT services and characteristics exposed by the smartwatchAffected if The device exposes BLE GATT services and characteristics without requiring authentication to access them
-
Test BLE GATT Write Request without authenticationSend a BLE GATT Write Request to a writable characteristic (such as those controlling notifications, alerts, or settings) using a BLE tool WITHOUT establishing any authenticated session or pairingAffected if The smartwatch accepts and processes BLE GATT Write Requests without requiring authentication, pairing, or any prior session establishment
-
Verify replay attack protectionCapture a BLE GATT Write Request packet, then attempt to replay the exact same packet to the device at a later time using a BLE tool; observe if the device accepts and executes the replayed commandAffected if The device accepts and processes replayed BLE GATT Write Requests, indicating missing sequence numbers, nonces, or other replay attack protections
-
Check session validation mechanismsExamine the BLE GATT communication for session tokens, challenge-response mechanisms, or sequence counters by analyzing the characteristic values or using a BLE sniffer to inspect packet structureAffected if The BLE GATT implementation lacks cryptographic session validation, challenge-response authentication, or sequence numbers in its write operations
The environment is affected if it contains a Fire-Boltt Smartwatch FB BGS001 running firmware MOY-JS14-2.0.4 where BLE GATT Write Requests can be sent and executed without authentication and replayed packets are accepted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement cryptographic session validation (e.g., token/nonce-based challenge-response), add sequence numbers to prevent replay attacks, require user confirmation for sensitive BLE commands, and enforce authentication before accepting GATT write operations.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37271 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-37271 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data