# CVE-2026-89034: TCH QRing R20_B006 Unauthenticated BLE Access

> Unauthenticated BLE access allows nearby attackers to bypass authentication and read sensitive health data from the smart ring.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/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:** 16 Sep 2026
- **Updated:** 19 Sep 2026
- **Also known as:** GHSA-2xqr-38g6-4hhr

## What is CVE-2026-89034?

CVE-2026-89034 is a high-severity authentication bypass vulnerability in TCH QRing, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TCH QRing smart ring model R20_B006 running firmware RT09R20_1.00.00_250318 contains an unauthenticated Bluetooth Low Energy access vulnerability that allows any nearby attacker to connect to the device without pairing, authentication, or user approval by exploiting the exposed Nordic UART Service which enforces no client authentication or command authorization. Attackers within Bluetooth Low Energy range can connect directly to the ring, bypassing the official application and cloud authentication, to read battery levels, activate live heart rate monitoring, and retrieve stored historical heart rate and blood oxygen records.

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

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


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

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

## Is CVE-2026-89034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89034 is a high-severity authentication bypass vulnerability in TCH QRing, published on 16 Sep 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-89034 exists.

Affected product: TCH QRing. 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-89034/ (Markdown: https://insights.sbomify.com/CVE-2026-89034/index.md)
```

## Sources

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

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