Vulnerability Database · OSS-Fuzz · Package report

c-blosc2: vulnerability history, versions and safety

c-blosc2 is a package in the OSS-Fuzz ecosystem. Vulert records 75 vulnerabilities for it across 57 releases, from Jul 2020 to May 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
75 vulnerabilities recorded H16 M51 U8
i
8 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on c-blosc2 i

Updated on 23 Oct 2026

Careful: 8 of the 75 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 75 vulnerabilities on record across 4 years, none in the last year.

What to do: Plan around the 8 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 75 over 4 years · 0 in the last year i
  • Latest disclosure 02 May 2025 i
  • Highest CVSS n/a i
  • With no published fix 8 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 c-blosc2, 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.

i
Version Vulert vulnerabilities Fix published Details
v2.21.1 H1 M7 No Details →
v2.21.0 H1 M7 No Details →
v2.20.0 H1 M7 No Details →
v2.19.1 H1 M7 No Details →
v2.19.0 H1 M7 No Details →
v2.18.0 H1 M7 No Details →
v2.17.1 H1 M7 No Details →
v2.17.0 H1 M7 No Details →
v2.16.0 H3 M7 No Details →
v2.15.2 H3 M7 No Details →
v2.15.1 H4 M7 No Details →
v2.15.0 H4 M7 No Details →
v2.14.4 H4 M7 No Details →
v2.14.3 H4 M7 No Details →
v2.14.2 H4 M7 No Details →
v2.14.1 H4 M7 No Details →
v2.14.0 H4 M7 No Details →
v2.13.2 H4 M7 No Details →
v2.13.1 H4 M7 No Details →
v2.13.0 H4 M7 No Details →
v2.12.0 H4 M7 No Details →
v2.11.3 H4 M7 No Details →
v2.11.2 H4 M7 No Details →
v2.11.1 H4 M7 No Details →
v2.11.0 H4 M7 No Details →
v2.10.5 H4 M7 No Details →
v2.10.4 H4 M8 No Details →
v2.10.3 H4 M8 No Details →
v2.10.2 H4 M8 No Details →
v2.10.1 H4 M8 No Details →
v2.10.0 H4 M8 No Details →
v2.9.3 H4 M8 No Details →
v2.9.2 H4 M9 No Details →
v2.9.1 H4 M9 No Details →
v2.9.0 H4 M9 No Details →
v2.8.0 H4 M9 No Details →
v2.7.1 H4 M9 No Details →
v2.7.0 H4 M9 No Details →
v2.6.1 H4 M9 No Details →
v2.6.0 H4 M9 No Details →
v2.5.0 H4 M9 No Details →
v2.4.3 H4 M9 No Details →
v2.4.2 H4 M9 No Details →
v2.4.1 H4 M9 No Details →
v2.4.0 H4 M9 No Details →
v2.3.1 H4 M9 No Details →
v2.3.0 H5 M9 No Details →
v2.2.0 H3 M9 No Details →
v2.1.1 H4 M18 No Details →
v2.1.0 H8 M20 U1 No Details →
v2.0.4 H9 M19 U1 No Details →
v2.0.3 H9 M19 U1 No Details →
v2.0.2 H9 M19 U1 No Details →
v2.0.1 H9 M19 U1 No Details →
v2.0.0 H9 M19 U1 No Details →
v2.0.0-rc2 H3 M15 U1 No Details →
v2.0.0.rc1 H3 M15 U1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 7
  • 2021 50
  • 2022 13
  • 2023 4
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for c-blosc2

The 5 most severe of 75 vulnerabilities recorded for this package

Search all 75 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-buffer-overflow in frame_get_metalayers in c-blosc2 N/A medium 7f4574f51ad7db56fc13de89e13e7893b1a82189 09 Apr 2022
Use-of-uninitialized-value in ZSTD_createDDict_advanced in c-blosc2 N/A medium a83f4780ccd23eee46541d5789b9be1c1f6f696c 22 Jul 2020
Heap-buffer Overflow Vulnerability in c-blosc2 Package N/A medium No fix published 02 May 2025
Heap-buffer-overflow in ndlz8_decompress in c-blosc2 N/A high ce2e8fe5f2fdb3779505935f05f93481d4905e62 18 Dec 2021
Heap-buffer-overflow in ndlz4_decompress in c-blosc2 N/A high 36fbefb68fd04d9399aec57e46f4ed44a84c39e1 17 Dec 2021

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 c-blosc2

Is c-blosc2 safe to use?

Vulert records 75 vulnerabilities for c-blosc2 in OSS-Fuzz: 0 critical, 16 high, 51 medium and 0 low, plus 8 not yet rated. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does c-blosc2 have?

75 vulnerabilities are recorded for c-blosc2 in the OSS-Fuzz ecosystem: 0 critical, 16 high, 51 medium and 0 low, plus 8 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 c-blosc2 vulnerabilities disclosed?

0 vulnerabilities were recorded for c-blosc2 in the last 12 months, and the oldest entry in this database dates to 14 Jul 2020. 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 c-blosc2 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 c-blosc2 for upcoming vulnerabilities?

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