CVE-2026-14297
8.7Nordic Semiconductor · nRF Connect SDK
A buffer overflow in the Bluetooth CGMS RACP write handler in the Nordic nRF Connect SDK allows an authenticated BLE peer to perform an out-of-bounds write to adjacent BSS memory.
Executive summary
A high-severity buffer overflow vulnerability in the Nordic nRF Connect SDK could allow an authenticated Bluetooth peer to corrupt system memory and potentially compromise device stability or integrity.
Vulnerability
This vulnerability is a buffer overflow (CWE-787) occurring within the Bluetooth Continuous Glucose Monitoring Service (CGMS) Record Access Control Point (RACP) write handler. The flaw allows an authenticated Bluetooth Low Energy (BLE) peer to trigger an out-of-bounds write of a 20-byte static buffer into adjacent BSS memory.
Business impact
The potential impact of this vulnerability is significant, as it allows for arbitrary memory corruption that could lead to unauthorized code execution or system crashes depending on the specific firmware layout. Given the CVSS score of 8.7, this vulnerability poses a severe risk to product reliability and data integrity, particularly for medical or industrial devices utilizing the nRF Connect SDK. Successful exploitation could result in service disruption or the total loss of control over the affected device.
Remediation
Immediate Action: Organizations should review the official Nordic Semiconductor security advisory and apply the recommended firmware updates or patches as soon as they are made available by the vendor.
Proactive Monitoring: Security teams should monitor Bluetooth traffic for anomalous RACP write requests or unexpected device behavior that may indicate an exploitation attempt.
Compensating Controls: Where patching is not immediately feasible, restrict Bluetooth access to authorized devices only and implement physical security measures to limit proximity-based attack vectors.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Due to the severity of this memory corruption flaw, it is critical that administrators prioritize the identification of all devices running the affected versions of the nRF Connect SDK. Once a vendor-provided update is released, it should be tested and deployed immediately to mitigate the risk of remote memory manipulation via Bluetooth.
Sources
Originally found and disclosed by https://github.com/V33RU, per the CVE Program record.