Raw vector
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-23750 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23750 is a heap-based buffer overflow vulnerability (CWE-122) affecting Golioth Pouch version 0.1.0 prior to commit 1b2219a1. The issue resides in the BLE GATT server certificate handling function server_cert_write(), which allocates a heap buffer of size CONFIG_POUCH_SERVER_CERT_MAX_LEN upon receiving the first fragment and then appends subsequent fragments via memcpy() without checking remaining capacity. This flaw has a CVSS v3.1 base score of 8.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), indicating high integrity and availability impacts but no confidentiality impact.
An adjacent Bluetooth Low Energy (BLE) client can exploit this vulnerability by sending unauthenticated certificate fragments whose total size exceeds the allocated buffer, triggering a heap overflow. Attackers require physical proximity (adjacent network access) but need no privileges or user interaction. Successful exploitation leads to a device crash due to memory corruption and potential integrity violations from overwritten heap data.
Mitigation is available via the upstream patch in commit 1b2219a1 at https://github.com/golioth/pouch/commit/1b2219a1. Additional details are provided in advisories from SecMate (https://secmate.dev/disclosures/SECMATE-2025-0018), VulnCheck (https://www.vulncheck.com/advisories/golioth-pouch-ble-gatt-heap-based-buffer-overflow), and a disclosure blog (https://blog.secmate.dev/posts/golioth-vulnerabilities-disclosure/). Security practitioners should update to the patched version and review BLE GATT handling in similar IoT firmware for analogous bounds-checking flaws.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-8870
Vulnerability Data
Golioth Pouch version 0.1.0, prior to commit 1b2219a1, contains a heap-based buffer overflow in BLE GATT server certificate handling. server_cert_write() allocates a heap buffer of size CONFIG_POUCH_SERVER_CERT_MAX_LEN when receiving the first fragment, then appends subsequent fragments using memcpy() without verifying…
more
that sufficient capacity remains. An adjacent BLE client can send unauthenticated fragments whose combined size exceeds the allocated buffer, causing a heap overflow and crash; integrity impact is also possible due to memory corruption.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.4.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.
Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.
Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.
Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.
Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.
Timely patching removes known heap-overflow instances after they exist.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect heap overflows before release.
Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.