CVE-2026-23748: Golioth Firmware SDK < 0.22.0 LightDB State Out-of-Bounds Read
Golioth Firmware SDK version 0.10.0 prior to 0.22.0, fixed in commit d7f55b38, contain an out-of-bounds read in LightDB State string parsing. When processing a string payload, a payload_size value less than 2 can cause a size_t underflow when computing the number of bytes to copy (nbytes). The subsequent memcpy() reads past the end of the network buffer, which can crash the device. The condition is reachable from on_payload, and golioth_payload_is_null() does not block payload_size==1. A malicious server or MITM can trigger a denial of service.
Security readout for executives and security teams
Plain-English summary
A flaw in older Golioth Firmware SDK builds can let a malicious server or man-in-the-middle crash an IoT device by sending a malformed LightDB State string payload. The known impact is device availability, not data theft or code execution, based on the supplied sources.
Executive priority
Treat this as a moderate availability risk for connected devices. Prioritize fleets where downtime creates operational cost, safety concerns, or field-service burden. Patch during the next controlled firmware update cycle unless exposed devices have high MITM or server-trust risk.
Technical view
In Golioth Firmware SDK 0.10.0 before 0.22.0, LightDB State string parsing can underflow a size_t when payload_size is less than 2. The resulting memcpy reads beyond the network buffer and may crash the device. The issue is reachable from on_payload and fixed in commit d7f55b38.
Likely exposure
Exposure is likely limited to firmware using affected Golioth Firmware SDK versions and LightDB State processing. Risk is higher where devices could receive payloads from an untrusted server path or a feasible MITM position.
Exploitation context
The source bundle says a malicious server or MITM can trigger denial of service. KEV is false, and the supplied sources do not establish active exploitation in the wild. Public technical details exist, including an exploit-tagged disclosure reference.
Researcher notes
The evidence supports CWE-191 integer underflow leading to out-of-bounds read and denial of service. The supplied affected-version data is somewhat terse, so validate exact dependency ranges against the vendor release and commit before broad fleet conclusions.
Mitigation direction
Upgrade affected firmware builds to Golioth Firmware SDK v0.22.0 or later.
Confirm commit d7f55b38 is included where version tags are unreliable.
Review Golioth release notes and Secmate disclosure for integration-specific guidance.
Prioritize remediation for devices with feasible server compromise or MITM exposure.
Validation and detection
Inventory firmware builds for Golioth Firmware SDK versions 0.10.0 through before 0.22.0.
Confirm LightDB State functionality is present and reachable in affected device firmware.
Verify patched builds include the fixed LightDB State string parsing code.
Check device crash telemetry for malformed payload handling failures.
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-191: 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.
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-191 · source CWE mapping
Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.