# CVE-2026-14297: Memory corruption in nRF Connect SDK

> An authenticated BLE peer can trigger a buffer overflow in the CGMS RACP handler, potentially leading to code execution or denial of service depending on memory layout.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-9789-mpm3-jqwq

## What is CVE-2026-14297?

CVE-2026-14297 is a high-severity memory corruption vulnerability in Nordic Semiconductor ASA nRF Connect SDK, published on 7 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A buffer overflow in the Bluetooth Continuous Glucose
     Monitoring Service (CGMS) Record Access Control Point (RACP) write handler
     allows an authenticated BLE peer to overflow a 20-byte static buffer into
     adjacent BSS memory. The exploitable impact cannot be predetermined - it
     is entirely dependent on the linker-assigned BSS layout of the specific
     firmware build, which may vary.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-14297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14297 is a high-severity memory corruption vulnerability in Nordic Semiconductor ASA nRF Connect SDK, published on 7 Sep 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-14297 in the wild and no public exploit code.

Affected product: Nordic Semiconductor ASA nRF Connect 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-14297/ (Markdown: https://insights.sbomify.com/CVE-2026-14297/index.md)
```

## Sources

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

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