CVE-2026-23750: Golioth Pouch (prior to commit 1b2219a1) BLE GATT Heap-based Buffer Overflow
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 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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23750 is a high-severity flaw in Golioth Pouch BLE certificate handling. A nearby attacker can send unauthenticated Bluetooth fragments that exceed an allocated heap buffer, causing device crashes and possible memory corruption. The business risk is highest for deployed devices using Pouch 0.1.0 or code before the fixing commit.
Executive priority
Treat as a priority fix for affected BLE-enabled device fleets. The attack requires proximity, but no credentials or user action, and successful exploitation can crash devices or corrupt memory.
Technical view
server_cert_write() allocates CONFIG_POUCH_SERVER_CERT_MAX_LEN for the first certificate fragment, then copies later fragments without checking remaining capacity. Overlong combined BLE GATT writes can trigger a heap-based buffer overflow. CVSS 8.1 reflects adjacent attack vector, low complexity, no privileges, no user interaction, high integrity and availability impact.
Likely exposure
Exposure appears limited to products or firmware using Golioth Pouch 0.1.0 or code before commit 1b2219a1, with the affected BLE GATT server certificate path enabled and reachable by adjacent BLE clients.
Exploitation context
Sources describe unauthenticated adjacent BLE exploitation and public technical details. The bundle marks KEV as false, so there is no provided evidence of known active exploitation in the wild.
Researcher notes
Key validation points are dependency version, presence of server_cert_write(), CONFIG_POUCH_SERVER_CERT_MAX_LEN handling, and whether cumulative fragment length is bounded before memcpy(). Do not infer internet exposure; the CVSS vector is adjacent network.
Mitigation direction
Update Golioth Pouch to include commit 1b2219a1 or a later vendor-fixed version.
Rebuild and redeploy affected firmware images after confirming the patched dependency is included.
Restrict BLE access during remediation where operationally feasible.
Check Golioth guidance for any additional fixed releases or configuration advice.
Validation and detection
Inventory firmware builds for Golioth Pouch 0.1.0 or pre-1b2219a1 source.
Confirm deployed images contain the 1b2219a1 fix or later equivalent changes.
Verify the affected BLE GATT certificate handling feature is disabled or patched.
Run defensive regression tests for certificate fragment length handling in an isolated lab.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.