Quick answers
- Is CVE-2026-26459 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26459 being exploited in the wild.
- How severe is CVE-2026-26459?
- High severity, with a CVSS score of 7.5, published 27 August 2026.
- Which products and versions are affected?
- Ipflavors Ccoap commit 77f55c4b466e99327c24ace8a2913d3ba7e2ccd5 and prior.
- Is there a fix for CVE-2026-26459?
- 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-26459 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-26459?
- 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 use-of-uninitialized-memory / invalid-memory-access bug in the coap_decode_option() function. When parsing COAP message options, the function allocates an option list via malloc() without initializing it, then partially initializes option structures. If option data is insufficient, it breaks from the parse loop before allocating memory for the data pointers, leaving them uninitialized (containing garbage). The cleanup function coap_clean_options() later attempts to free these uninitialized pointers, causing a segmentation fault. The attack requires sending a malformed COAP message to an application using the vulnerable library; no authentication or special privileges are needed. An attacker on the network can trigger a denial of service by crashing any service using ccoap.
Affected products
- ipflavors ccoap commit 77f55c4b466e99327c24ace8a2913d3ba7e2ccd5 and prior
Timeline
- 2026-08-27: disclosed