Libcoap Contains Out-of-bounds Read Vulnerabilities
Affects libcoapSource GCVE Database
Not known to be exploited · CVSS 9.8 Critical.
Data as of 17 Nov 2026, 20:48 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10libcoap3pkg:deb/ubuntu/libcoap3?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlibcoap3pkg:deb/ubuntu/libcoap3?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 25.10libcoap3pkg:deb/ubuntu/libcoap3?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlibcoap3pkg:deb/ubuntu/libcoap3?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSlibcoap3pkg:deb/ubuntu/libcoap3?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSlibcoappkg:deb/ubuntu/libcoap?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, users should consider mitigating exposure by restricting access to vulnerable libcoap services or disabling OSCORE features if feasible.
Description
libcoap versions including 4.1.2-1 through 4.3.5-1 contain critical out-of-bounds read vulnerabilities in the OSCORE Appendix B.2 CBOR unwrap handling. The function get_byte_inc() in src/oscore/oscore_cbor.c relies solely on assert() for bounds checking, which is disabled in release builds compiled with NDEBUG. This allows attackers to send crafted CoAP requests with malformed OSCORE options or responses during OSCORE negotiation to trigger out-of-bounds reads and potentially cause memory corruption via integer wraparound in allocation size computation.