# CVE-2026-5706: Buffer overflow in Bluetooth Mesh SDK when handling extended advertisements

> Remote attackers with network access can trigger stack corruption and execute code via malformed extended advertisements in the Bluetooth Mesh SDK.

- **Severity:** High 8.9 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA: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:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-f29w-mc54-fh2c

## What is CVE-2026-5706?

CVE-2026-5706 is a high-severity memory corruption vulnerability in Silicon Labs BT Mesh SDK, published on 27 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Bluetooth Mesh SDK 6.1.4 and earlier, malformed extended advertisements can trigger out-of-bounds writes leading to stack corruption and remote code execution. These messages must come from a device that has already joined the network. Only provisioners supporting extended advertisements may be impacted.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

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

## Is CVE-2026-5706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5706 is a high-severity memory corruption vulnerability in Silicon Labs BT Mesh SDK, published on 27 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-5706 in the wild and no public exploit code.

Affected product: Silicon Labs BT Mesh SDK. 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-5706/ (Markdown: https://insights.sbomify.com/CVE-2026-5706/index.md)
```

## Sources

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

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