VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

wavpack: vulnerability history, versions and safety

wavpack is a package in the OSS-Fuzz ecosystem. Vulert records 9 vulnerabilities for it across 6 affected ranges, from Jun 2020 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H1 M8
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

See all wavpack vulnerabilities

Vulert verdict on wavpack i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 15 Feb 2025. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 9 vulnerabilities on record across 4 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 9 over 4 years · 0 in the last year i
  • Latest disclosure 15 Feb 2025 i
  • Highest CVSS n/a i
  • With no published fix 0 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from b7b796375293defeae340e83d066efa33fa0d2f3 up to 84b576d2c627418a6453cc986b53e79bed38d653 (exclusive) 1
from 348ff60b489e731ffd046f837500313499623e3e up to 4cb11c66de6cc759e57508d38df4956fe4bb3311 (exclusive) 1
from 348ff60b489e731ffd046f837500313499623e3e up to db878b73e76c14842e99ad05aed9338d495703c0 (exclusive) 1
from 540cdc7a5afb0884f4732735b43f9ababf658789 up to eefe90e7724a0ffce730655f417e34336b6d0a2b (exclusive) 1
from 109a35ecb400580983790961c9066bb1449185db up to c4e193f3a360817eb097fb54f2f9f84d5dda7112 (exclusive) 1
from b7b796375293defeae340e83d066efa33fa0d2f3 up to c3fd0514a45fb79096105c64205ae98cd607755e (exclusive) 4

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2025 5

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

03 Vulnerabilities

Recorded vulnerabilities for wavpack

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Use-of-uninitialized-value in decimate_dsd_run in wavpack N/A medium db878b73e76c14842e99ad05aed9338d495703c0 22 Jul 2020
Use-of-uninitialized-value in decimate_dsd_run in WavPack N/A medium 4cb11c66de6cc759e57508d38df4956fe4bb3311 22 Jul 2020
Use-of-uninitialized-value in WavpackDeleteTagItem N/A medium c4e193f3a360817eb097fb54f2f9f84d5dda7112 26 Jun 2020
UNKNOWN READ vulnerability in WavPack N/A medium eefe90e7724a0ffce730655f417e34336b6d0a2b 24 Jun 2020
Uninitialized Value Use in WavPack: Vulnerability OSV-2025-108 N/A medium 84b576d2c627418a6453cc986b53e79bed38d653 10 Feb 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 wavpack

Is wavpack safe to use?

Vulert records 9 vulnerabilities for wavpack in OSS-Fuzz: 0 critical, 1 high, 8 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does wavpack have?

9 vulnerabilities are recorded for wavpack in the OSS-Fuzz ecosystem: 0 critical, 1 high, 8 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new wavpack vulnerabilities disclosed?

0 vulnerabilities were recorded for wavpack in the last 12 months, and the oldest entry in this database dates to 24 Jun 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 wavpack 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 wavpack for upcoming vulnerabilities?

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