Skip to main content
CVE-2024-26134VulnerabilityPublished Updated

SUSE · Security update for python-cbor2

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited · fixed in SUSE package updates : patch SUSE soon.

Data as of 16 Nov 2026, 00:35 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Patch
Available – fixed in 5.6.3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

AI-suggested

Upgrade python-cbor2 to version 5.6.3 or later, which includes the fix for CVE-2024-26134. For CVE-2025-64076, apply the security update provided by the vendor that addresses the chunk length calculation bug. Since the fixes are available, applying these updates will remediate the vulnerabilities.

Description

This security update for python-cbor2 addresses two vulnerabilities. CVE-2025-64076 fixes a bug in the decode_definite_long_string() function that caused incorrect chunk length calculation. CVE-2024-26134, already fixed in release 5.6.3, resolves a potential crash when hashing a CBORTag. Both issues could impact the stability and correctness of the python-cbor2 library.

References

Community reviews

Loading reviews…