Vulnerability · Published Mar 23, 2026 · Assigned by GitHub_M
CVE-2026-26209cbor2 has a Denial of Service via Uncontrolled Recursion in cbor2.loads
High 7.5
In plain English
A high-severity security flaw in cbor2 from agronholm. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 34% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | cbor2 | no fix listed | DEBIAN-CVE-2026-26209 |
| Debian:13 | cbor2 | no fix listed | DEBIAN-CVE-2026-26209 |
| Debian:14 | cbor2 | 5.9.0-1 | DEBIAN-CVE-2026-26209 |
| PyPI | cbor2 | 5.9.0 | GHSA-3c37-wwvx-h642 |
| PyPI | cbor2 | 5.9.0 | PYSEC-2026-2123 |
| Ubuntu:22.04:LTS | cbor2 | no fix listed | UBUNTU-CVE-2026-26209 |
| Ubuntu:24.04:LTS | cbor2 | no fix listed | UBUNTU-CVE-2026-26209 |
| Ubuntu:25.10 | cbor2 | no fix listed | UBUNTU-CVE-2026-26209 |
| Ubuntu:26.04:LTS | cbor2 | no fix listed | UBUNTU-CVE-2026-26209 |
| Ubuntu:26.10 | cbor2 | no fix listed | UBUNTU-CVE-2026-26209 |
Affected products (as reported)
Weakness: CWE-674 · Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
References
- https://github.com/agronholm/cbor2/security/advisories/GHSA-3c37-wwvx-h642 x_refsource_CONFIRM
- https://github.com/agronholm/cbor2/pull/275 x_refsource_MISC
- https://github.com/agronholm/cbor2/commit/e61a5f365ba610d5907a0ae1bc72769bba34294b x_refsource_MISC
- https://github.com/agronholm/cbor2/releases/tag/5.9.0 x_refsource_MISC