Vulnerability · Published Oct 12, 2026 · Assigned by VulnCheck
CVE-2020-37280cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths
High 7.5
In plain English
A high-severity security flaw in cbor-sync from PelionIoT. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 45% of all known vulnerabilities).
Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.5%top 54.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known
Official description
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.
Affected products (as reported)
Weakness: CWE-789 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
- GitHub Pull Request #4 issue-tracking, patch
- GitHub Issue #6 issue-tracking
- https://github.com/PelionIoT/cbor-sync product
- VulnCheck Advisory: cbor-sync through 1.0.4 Memory Exhaustion via Unchecked CBOR Array Lengths third-party-advisory