Critical Vulnerability in Audiofile Package: CVE-2025-50950

audiofile Updated 24 Oct 2025

Summary

23/10/2025
N/A
No i
Unrated
Not published

DEBIAN-CVE-2025-50950: ... Affects audiofile versions 0.3.6-5 – 0.3.6-7. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Audiofile package is a library designed for manipulating audio file formats. It provides functionalities for reading and writing various audio file types, making it a crucial component for applications that handle audio data. However, it has been identified to have a vulnerability that affects multiple versions across different Debian releases, potentially exposing systems to security risks.

Vulnerability Detail

CVE-2025-50950 is a critical vulnerability found in the Audiofile package, which allows attackers to exploit the system by manipulating audio files. The vulnerability originates from improper handling of audio data, which could lead to arbitrary code execution or denial of service. This poses significant risks, especially for applications that rely on Audiofile for audio processing, as it could allow unauthorized access or disruption of services.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If an immediate update is not possible, consider disabling any features that utilize the Audiofile package or restricting access to applications that depend on it until a patch is applied. Additionally, monitor your systems for any unusual activity that may indicate exploitation of this vulnerability.

Conclusion

CVE-2025-50950 poses a significant risk to systems using the Audiofile package across multiple Debian versions. It is crucial for users to update their packages promptly and consider workarounds if immediate updates are not feasible. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications.

See every vulnerability recorded for audiofile →

Share this vulnerability

FAQ

CVE-2025-50950 is a critical vulnerability in the Audiofile package that could allow attackers to execute arbitrary code or cause denial of service.

The vulnerability affects all versions of the Audiofile package across Debian 11, 12, 13, and 14.

You can use Vulert, which monitors open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json to Vulert, you can check for vulnerabilities in real-time.

Consider disabling features that use the Audiofile package or restricting access to applications that depend on it until a patch is available.

Detailed information about CVE-2025-50950 can be found in the Debian security advisories and on the official CVE database.

Related vulnerabilities

Recent vulnerabilities recorded for audiofile.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

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 →
Help improve this record
Report an issue or send feedback