VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

cbor2: vulnerability history, versions and safety

cbor2 is a package in the Debian ecosystem. Vulert records 3 vulnerabilities for it across 22 releases, from Nov 2025 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded U3
i
3 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 23 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cbor2 vulnerabilities

Vulert verdict on cbor2 i

Updated on 23 Oct 2026

Careful: 3 of the 3 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

Long-term outlook: usable, but needs attention 3 vulnerabilities on record across 1 year, 3 in the last year.

What to do: Plan around the 3 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 3 in the last year i
  • Latest disclosure 23 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 3 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for cbor2, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 22 of 22 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cbor2

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Integer Underflow and Memory Leak Vulnerabilities in cbor2 Package 7.5 high No fix published 18 Nov 2025
Denial of Service Vulnerability in cbor2 Package: Uncontrolled Recursion in CBOR Decoding 7.5 high No fix published 23 Mar 2026
Memory Persistence Vulnerability in cbor2 Package Allows Data Leakage N/A unrated No fix published 31 Dec 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About cbor2

Is cbor2 safe to use?

Vulert records 3 vulnerabilities for cbor2 in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does cbor2 have?

3 vulnerabilities are recorded for cbor2 in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 3 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cbor2 vulnerabilities disclosed?

3 vulnerabilities were recorded for cbor2 in the last 12 months, and the oldest entry in this database dates to 18 Nov 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cbor2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor cbor2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cbor2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.