# CVE-2026-19292: Bluetooth re-pairing with legitimate device can use lower security level

> Attackers can brute-force Bluetooth Long Term Keys by forcing re-pairing at a lower security level, compromising device authentication.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-pv8r-xmqx-g2r9

## What is CVE-2026-19292?

CVE-2026-19292 is a high-severity vulnerability in silabs.com WiseConnect, published on 13 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Re-pairing with a legitimate device can use a lower security level than
previous making brute-forcing the LTK easier. See V4 in the BLERP paper linked below.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

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

## Is CVE-2026-19292 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19292 is a high-severity vulnerability in silabs.com WiseConnect, published on 13 Aug 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-19292 in the wild and no public exploit code.

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

## Sources

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

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