Quick answers
- Is CVE-2026-26452 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-26452 being exploited in the wild.
- How severe is CVE-2026-26452?
- 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-26452?
- 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-26452 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-26452?
- 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 segmentation fault (memory safety issue) in ccoap's option parsing logic that occurs when processing CoAP messages containing invalid option numbers. The root cause is improper bounds checking or validation of option numbers during message parsing. The attack vector is network-based: an attacker can send a malformed CoAP message to a system running vulnerable ccoap, triggering the crash without authentication. The impact is denial of service—affected devices become unresponsive. A patch status is unknown from the advisory text.
Affected products
- ipflavors ccoap commit 77f55c4b466e99327c24ace8a2913d3ba7e2ccd5
Timeline
- 2026-08-27: disclosed