🛡️ CVE-2025-64076 on Debian — cbor2
Description
Multiple vulnerabilities exist in cbor2 through version 5.7.0 in the decode_definite_long_string() function of the C extension decoder (source/decoder.c): (1) Integer Underflow Leading to Out-of-Bounds Read (CWE-191, CWE-125): An incorrect variable reference and missing state reset in the chunk processing loop causes buffer_length to not be reset to zero after UTF-8 character consumption. This results in subsequent chunk_length calculations producing negative values (e.g., chunk_length = 65536 - buffer_length), which are passed as signed integers to the read() method, potentially triggering unlimited read operations and resource exhaustion. (2) Memory Leak via Missing Reference Count Release (CWE-401): The main processing loop fails to release Python object references (Py_DECREF) for chunk objects allocated in each iteration. For CBOR strings longer than 65536 bytes, this causes cumulative memory leaks proportional to the payload size, enabling memory exhaustion attacks through repeated processing of large CBOR payloads. Both vulnerabilities can be exploited remotely without authentication by sending specially-crafted CBOR data containing definite-length text strings with multi-byte UTF-8 characters positioned at 65536-byte chunk boundaries. Successful exploitation results in denial of service through process crashes (CBORDecodeEOF exceptions) or memory exhaustion. The vulnerabilities affect all applications using cbor2's C extension to process untrusted CBOR data, including web APIs, IoT data collectors, and message queue processors. Fixed in commit 851473490281f82d82560b2368284ef33cf6e8f9 pushed with released version 5.7.1.
Distribution advisory
This page covers CVE-2025-64076 as tracked by Debian, for the package cbor2. The fix is available in version 5.7.1-1; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
Affected software
DEBIAN-CVE-2025-64076 is recorded against 1 package.
- cbor2 (fixed in 5.7.1-1)
Timeline and source
Published on 18 November 2025 and last revised on 4 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2025-64076 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| cbor2 | — | 5.7.1-1 |
References
Similar Threats
- High ROOT-APP-PYPI-CVE-2025-68131
- High ROOT-APP-PYPI-CVE-2026-26209
- High CVE-2026-26209
- Unknown DEBIAN-CVE-2026-26209
- Unknown UBUNTU-CVE-2026-26209
More DEBIAN CVE 2025 advisories
Browse all of DEBIAN CVE 2025 in the advisory index.
- DEBIAN-CVE-2025-63261
- DEBIAN-CVE-2025-63396
- DEBIAN-CVE-2025-63498
- DEBIAN-CVE-2025-63499
- DEBIAN-CVE-2025-63757
- DEBIAN-CVE-2025-63811
- DEBIAN-CVE-2025-63829
- DEBIAN-CVE-2025-63938
- DEBIAN-CVE-2025-64098
- DEBIAN-CVE-2025-64170
- DEBIAN-CVE-2025-64181
- DEBIAN-CVE-2025-64329
- DEBIAN-CVE-2025-64330
- DEBIAN-CVE-2025-64331
- DEBIAN-CVE-2025-64332
- DEBIAN-CVE-2025-64333
Site Security Check
Is cbor2 part of your stack?
DEBIAN-CVE-2025-64076 is rated CVSS 7.5 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.