VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

audiofile: vulnerability history, versions and safety

audiofile is a package in the Debian ecosystem. Vulert records 42 vulnerabilities for it across 4 releases, from Jan 2009 to Oct 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
42 vulnerabilities recorded U42
i
1 with no fix published

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

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

Most recent disclosure 23 Oct 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all audiofile vulnerabilities

Vulert verdict on audiofile i

Updated on 23 Oct 2026

Careful: one of the 42 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

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

What to do: Plan around the 1 vulnerability 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 42 over 16 years · 1 in the last year i
  • Latest disclosure 23 Oct 2025 i
  • Highest CVSS 8.8 i
  • With no published fix 1 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 audiofile, 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
0.3.6-7 U1 No Details →
0.3.6-6 U1 No Details →
0.3.6-5 U6 No Details →
0.3.6-5+deb11u1 U1 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2009 2
  • 2017 26
  • 2018 4
  • 2019 2
  • 2020 2
  • 2022 2
  • 2023 2
  • 2025 2

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

03 Vulnerabilities

Recorded vulnerabilities for audiofile

The 5 most severe of 42 vulnerabilities recorded for this package

Search all 42 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-based Buffer Overflow in mpruett Audio File Library 8.8 high 0.3.6-5 16 Sep 2018
Buffer Overflow Vulnerability in Audiofile Package: CVE-2015-7747 8.8 high 0.3.6-3 19 Feb 2020
Heap-Based Buffer Overflow in AudioFile Package: CVE-2017-6828 7.8 high 0.3.6-4 15 Mar 2017
Heap-Based Buffer Overflow in Audiofile Package - CVE-2017-6827 7.8 high 0.3.6-4 15 Mar 2017
NULL Pointer Dereference in audiofile Audio File Library 0.3.6 6.5 medium 0.3.6-5 08 Jul 2018

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 audiofile

Is audiofile safe to use?

Vulert records 42 vulnerabilities for audiofile in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 42 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does audiofile have?

42 vulnerabilities are recorded for audiofile in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 42 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 audiofile vulnerabilities disclosed?

1 vulnerability was recorded for audiofile in the last 12 months, and the oldest entry in this database dates to 02 Jan 2009. 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 audiofile 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 audiofile for upcoming vulnerabilities?

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