High 7.5Published Oct 12, 2026

CVE-2020-37280cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths

Updated under an hour ago (2026-10-19 09:30 UTC)

Does this affect you?

It affects PelionIoT cbor-sync. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.54%, higher than 44% of scored CVEs.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for PelionIoT cbor-sync

Exploited in the last 30 days

cbor-sync through 1.0.4 contains a resource exhaustion vulnerability in CBOR.decode that trusts declared array and map lengths without checking remaining input. Remote attackers can supply a tiny crafted CBOR payload declaring huge lengths to drive billions of iterations, exhausting CPU and process memory.

CVSS: 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): CWE-789
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): 0.54% (percentile 44)
Assigned by: VulnCheck
NVD analysis: Deferred
Record last updated: Oct 13, 2026
First seen by InfoSec Signals: Oct 12, 2026

Affected products

Affected products

PelionIoT cbor-sync pelioniot:cbor_sync (from the name)	through 1.0.4	CNA record

References

https://github.com/PelionIoT/cbor-sync/pull/4issue-tracking, patch
https://github.com/PelionIoT/cbor-sync/issues/6issue-tracking
https://github.com/PelionIoT/cbor-syncproduct
https://www.vulncheck.com/advisories/cbor-sync-through-1.0.4-memory-exhaustion-via-unchecked-cbor-array-lengthsthird-party-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.