Device crash via unchecked certificate fragment append
Published Feb 26, 2026 · Updated Feb 26, 2026
Heap-based buffer overflow in Golioth Pouch 0.1.0 allows physically proximate attackers to crash devices through BLE certificate writes. The server_cert_write() handler allocates CONFIG_POUCH_SERVER_CERT_MAX_LEN bytes for the first fragment, then memcpy() appends later fragments without checking their cumulative length. Any connected BLE client can write without pairing, bonding, or encryption; oversized fragment sequences corrupt the heap, causing a crash and possible integrity loss.
Summary
What happened
Heap-based buffer overflow in Golioth Pouch 0.1.0 allows physically proximate attackers to crash devices through BLE certificate writes. The server_cert_write() handler allocates CONFIG_POUCH_SERVER_CERT_MAX_LEN bytes for the first fragment, then memcpy() appends later fragments without checking their cumulative length. Any connected BLE client can write without pairing, bonding, or encryption; oversized fragment sequences corrupt the heap, causing a crash and possible integrity loss.
The record
- CVE
- CVE-2026-23750
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Golioth
- Product
- Golioth Pouch
- Classifications
- CWE-122, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo