CVE-2026-29013
Out-of-bounds read in OSCORE CBOR parsing may lead to heap overflow.
Is CVE-2026-29013 being exploited?
Not confirmed. CVE-2026-29013 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-29013?
CVE-2026-29013 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-29013?
Yes. A fix has been recorded for CVE-2026-29013. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What should I do about CVE-2026-29013?
Upgrade libcoap to patched release when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can trigger CBOR parsing OOB read during OSCORE negotiation; potential heap overflow.
Patch when possible
- affected< v4.3.5b
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.