CVE-2026-26209

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. 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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

March 23, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Denial of Service in cbor2 via Deeply Nested CBOR Structures · Advisory · agronholm/cbor2 · GitHub

https://github.com/agronholm/cbor2/security/advisories/GHSA-3c37-wwvx-h642
github_release Patch Available

5.9.0

Patch available: agronholm/cbor2 5.9.0

https://github.com/agronholm/cbor2/releases/tag/5.9.0
github_pr Patch Available

Set default read_size to 1 for backwards compatibility

Patch available: agronholm/cbor2 5.9.0 (PR #275 merged 2026-02-28)

https://github.com/agronholm/cbor2/pull/275
github_commit Patch Available

commit e61a5f365ba6 (agronholm/cbor2)

Patch available: agronholm/cbor2 5.9.0 (contains commit e61a5f365ba6)

https://github.com/agronholm/cbor2/commit/e61a5f365ba610d5907a0ae1bc72769bba34294b

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-cuda-rhel9:17792236542026-05-20redhat
redhatrhaiis/vllm-rocm-rhel9:17792236512026-05-20redhat
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/vllm-rocm-rhel9:17782445312026-05-11redhat
redhatrhaiis/vllm-cuda-rhel9:17782746662026-05-11redhat

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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
cbor25.2.0-4 ... 6.1.2-2 (27 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
cbor25.4.6-1 ... 6.1.2-2 (20 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
cbor25.6.5-1 ... 6.1.2-2 (12 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
cbor25.6.5-1 ... 5.8.0-3 (6 versions)5.9.0-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
cbor21.0.0 ... 5.8.0 (40 versions)5.9.0

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:07 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 16:08 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 53 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 10:46 UTCEG score recompute
  8. 2026-08-16 10:46 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 19:45 UTCVendor advisory
  12. 2026-08-14 06:57 UTCEG score recompute
  13. 2026-08-14 06:57 UTCVendor advisory
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 21:39 UTCEG score recompute
  16. 2026-08-12 21:39 UTCVendor advisory
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-11 21:13 UTCEG score recompute
  19. 2026-08-11 21:13 UTCVendor advisory
  20. 2026-08-11 13:42 UTCEPSS rescore
  21. 2026-08-11 04:16 UTCEG score recompute
  22. 2026-08-11 04:16 UTCVendor advisory
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 04:36 UTCVendor advisory
  25. 2026-08-09 17:34 UTCEG score recompute
  26. 2026-08-09 17:34 UTCVendor advisory
  27. 2026-08-09 13:46 UTCEPSS rescore
  28. 2026-08-09 06:33 UTCEG score recompute
  29. 2026-08-09 06:33 UTCVendor advisory
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-08 03:56 UTCVendor advisory
  32. 2026-08-07 16:55 UTCEG score recompute
  33. 2026-08-07 16:55 UTCVendor advisory
  34. 2026-08-06 19:11 UTCEG score recompute
  35. 2026-08-06 19:11 UTCVendor advisory
  36. 2026-08-06 13:46 UTCEPSS rescore
  37. 2026-08-06 01:17 UTCEG score recompute
  38. 2026-08-06 01:17 UTCVendor advisory
  39. 2026-08-05 19:17 UTCEPSS rescore
  40. 2026-08-04 15:10 UTCEPSS rescore
  41. 2026-08-04 00:00 UTCEG score recompute
  42. 2026-08-04 00:00 UTCVendor advisory
  43. 2026-08-03 10:36 UTCEPSS rescore
  44. 2026-08-02 15:54 UTCEG score recompute
  45. 2026-08-02 15:54 UTCVendor advisory
  46. 2026-08-02 02:26 UTCEPSS rescore
  47. 2026-08-01 04:16 UTCEPSS rescore
  48. 2026-07-30 16:27 UTCEPSS rescore
  49. 2026-07-30 01:30 UTCEPSS rescore
  50. 2026-07-28 15:36 UTCEPSS rescore
  51. 2026-07-27 12:50 UTCEG score recompute
  52. 2026-07-27 12:50 UTCVendor advisory
  53. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-26209?
CVE-2026-26209 is a high vulnerability published on March 23, 2026. 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…
When was CVE-2026-26209 disclosed?
CVE-2026-26209 was first published in the National Vulnerability Database on March 23, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26209 actively exploited?
CVE-2026-26209 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.3% of all scored CVEs.
What is the CVSS score of CVE-2026-26209?
CVE-2026-26209 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-26209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26209, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26209

Explore →

Is Your Infrastructure Affected by CVE-2026-26209?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.