cbor2: cbor2 provides encoding and decoding for the Concise Binary Object Representation (CBOR) serialization format
CVE-2026-26209 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2026-26209, released March 23, 2026. It is not reported as exploited. Patch Radar priority: High.
cbor2 provides encoding and decoding for the Concise Binary Object Representation (CBOR) serialization format. Versions prior to 5.9.0 are vulnerable to a Denial of Service (DoS) attack caused by uncontrolled recursion when decoding deeply nested CBOR structures. This vulnerability affects both the pure Python implementation and the C extension `_cbor2`. The C extension relies on Python's internal recursion limits `Py_EnterRecursiveCall` rather than a data-driven depth limit, meaning it still raises `RecursionError` and crashes the worker process when the limit is hit. While the library handles moderate nesting levels, it lacks a hard depth limit. An attacker can supply a crafted CBOR payload containing approximately 100,000 nested arrays `0x81`. When `cbor2.loads()` attempts to parse this, it hits the Python interpreter's maximum recursion depth or exhausts the stack, causing the process to crash with a `RecursionError`. Because the library does not enforce its own limits, it allows an external attacker to exhaust the host application's stack resource. In many web application servers (e.g., Gunicorn, Uvicorn) or task queues (Celery), an unhandled `RecursionError` terminates the worker process immediately. By sending a stream of these small (<100KB) malicious packets, an attacker can repeatedly crash worker processes, resulting in a complete Denial of Service for the application. Version 5.9.0 patches the issue.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| cbor2 · Debian 14 | 5.9.0-1 | DEBIAN-CVE-2026-26209 | Mar 23, 2026 |
| python-cbor2 · opensuse-leap 16.0 | 5.6.5-160000.4.1 | OPENSUSE-SU-2026:20468-1 | Apr 7, 2026 |
| python-cbor2 · sles 16.0 | 5.6.5-160000.4.1 | SUSE-SU-2026:21139-1 | Apr 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.