Quick answers
- Is CVE-2026-26457 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26457 being exploited in the wild.
- How severe is CVE-2026-26457?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- Ipflavors Ccoap commit 77f55c4b466e99327c24ace8a2913d3ba7e2ccd5.
- Is there a fix for CVE-2026-26457?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-26457 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-26457?
- Check whether you run Ipflavors Ccoap at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a null pointer dereference in the coap_dump_msg() function in lib/ccoap/coap.c. The root cause occurs when processing CoAP messages with options of zero length: the coap_decode_option() function calls malloc(0), which may return NULL on some systems. The coap_dump_msg() function later attempts to call memcpy() on this NULL pointer without validating it first, resulting in a segmentation fault. The vulnerability requires the attacker to send a crafted CoAP message containing an option with zero length to an application using the affected library. No authentication or special privileges are required; the attack is network-reachable. The impact is denial of service through application crash. A patch must add a NULL pointer check before the memcpy() call in coap_dump_msg().
Affected products
- ipflavors ccoap commit 77f55c4b466e99327c24ace8a2913d3ba7e2ccd5
Timeline
- 2026-08-27: disclosed
- 2026-08-27: advisory: CVE-2026-26457