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.
CVE-2026-26209
This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(low)
- EG Risk
- 49(Attend)EG Risk 49/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 34%
- KEV
- Not listed
Published
March 23, 2026
Last Modified
June 17, 2026
References (4)
- security-advisories@githubhttps://github.com/agronholm/cbor2/commit/e61a5f365ba610d5907a0ae1bc72769bba34294b
- security-advisories@githubhttps://github.com/agronholm/cbor2/pull/275
- security-advisories@githubhttps://github.com/agronholm/cbor2/releases/tag/5.9.0
- security-advisories@githubhttps://github.com/agronholm/cbor2/security/advisories/GHSA-3c37-wwvx-h642
Vendor Advisories for CVE-2026-26209(5)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2026:19725Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (ROCm)
- RHSA-2026:19724Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AI Inference Server 3.2.2 (CUDA)
- RHSA-2026:16174Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AI Inference Server 3.3.3 (Spyre)
- RHSA-2026:16030Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AI Inference Server 3.3.3 (CUDA)
- RHSA-2026:16009Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AI Inference Server 3.3.3 (ROCm)
Patch Availability(5)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhaiis/vllm-cuda-rhel9:1779223654 | 2026-05-20 | redhat |
| redhat | rhaiis/vllm-rocm-rhel9:1779223651 | 2026-05-20 | redhat |
| redhat | rhaiis/vllm-spyre-rhel9:1778244546 | 2026-05-12 | redhat |
| redhat | rhaiis/vllm-rocm-rhel9:1778244531 | 2026-05-11 | redhat |
| redhat | rhaiis/vllm-cuda-rhel9:1778274666 | 2026-05-11 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Frequently asked(5)
What is CVE-2026-26209?
When was CVE-2026-26209 disclosed?
Is CVE-2026-26209 actively exploited?
What is the CVSS score of CVE-2026-26209?
How do I remediate CVE-2026-26209?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-26209
Is Your Infrastructure Affected by CVE-2026-26209?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.