# CVE-2026-65932: BT122 stops advertising

> An attacker can cause the BT122 Bluetooth module to stop advertising by sending a specific plaintext message, resulting in a denial of service.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-3j2f-xg4w-894p

## What is CVE-2026-65932?

CVE-2026-65932 is a medium-severity denial of service vulnerability in silabs.com BT122, 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

The BT122 module stops advertising after receiving a plaintext 'pause enceryption response' message resulting in a denial of service. See vulnerability B-E2 in the related paper below.

Weakness: CWE-440 (Expected Behavior Violation)

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


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

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

## Is CVE-2026-65932 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65932 is a medium-severity denial of service vulnerability in silabs.com BT122, 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-65932 in the wild and no public exploit code.

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

## Sources

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

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