CVE-2025-64076

Exp

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.

Published: 2025-11-18 Last update: 2025-12-31 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-64076 is rated High Exploit Risk (61.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.24%). Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2025-64076

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2025-64076

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-16 0.33% 0.24% -0.09%
2 2026-03-20 0.18% 0.33% +0.14%
3 2025-12-31 0.18%

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-64076

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]

Weakness enumeration for CVE-2025-64076

OS Trackers for CVE-2025-64076

vendor priority summary link
alpine CVE-2025-64076: 1 source package rows (py3-cbor2); 3 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2025-64076
debian unimportant CVE-2025-64076 unimportant priority: Debian including 1 source packages (cbor2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2025-64076
redhat high https://access.redhat.com/security/cve/CVE-2025-64076
suse high https://www.suse.com/security/cve/CVE-2025-64076/
ubuntu medium CVE-2025-64076 medium priority: Ubuntu including 1 source packages (cbor2), 5 status rows across 5 suites (jammy, noble, plucky, questing, upstream): needs-triage 3, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-64076

Affected software / configurations for CVE-2025-64076

Vendor Product Version Raw CPE
agronholm cbor2 <= 5.7.0 cpe:2.3:a:agronholm:cbor2:*:*:*:*:*:python:*:*

References for CVE-2025-64076

cvelogic Threat Intelligence