CVE-2018-19800: aubio Buffer Overflow vulnerability

aubio Updated 02 Oct 2025

Summary

26/07/2019
Yes i
Critical
9.8

CVE-2018-19800: aubio Buffer Overflow vulnerability. Affects aubio versions >= 0.4.0, < 0.4.9. Fixed in 0.4.9. How to fix ↓

Also tracked for

The same CVE-2018-19800 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

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

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 aubio package is a Python library for audio analysis. It provides various functions and algorithms for tasks such as pitch detection, beat tracking, and tempo estimation. This vulnerability affects versions 0.4.0 to 0.4.8 of the package. The specific function new_aubio_tempo is susceptible to a Buffer Overflow.

Vulnerability Detail

The Buffer Overflow vulnerability in new_aubio_tempo allows an attacker to overwrite adjacent memory locations, potentially leading to arbitrary code execution or a system crash. This can be exploited by providing malicious input to the function, causing it to write beyond the allocated buffer. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8. It is important to note that this vulnerability has been reviewed and confirmed by GitHub.

How To Fix

Latest published version: 0.4.9 as of 23 Oct 2026

pip install --upgrade "aubio==0.4.9"

The newest release already contains this fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a workaround, users can avoid using the vulnerable function new_aubio_tempo until they are able to upgrade to the fixed version. Alternatively, they can implement input validation and bounds checking in their own code to prevent potential buffer overflows.

Conclusion

The aubio Buffer Overflow vulnerability in the new_aubio_tempo function can have severe consequences, including arbitrary code execution and system crashes. It is crucial to upgrade to version 0.4.9 or later of the aubio package to mitigate this vulnerability. If you require further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for aubio →

Share this vulnerability

FAQ

A Buffer Overflow vulnerability occurs when a program writes data beyond the allocated buffer, overwriting adjacent memory locations. This can lead to various security issues, including arbitrary code execution or system crashes.

This vulnerability can be exploited by providing malicious input to the new_aubio_tempo function, causing it to write beyond the allocated buffer. An attacker can craft input that triggers this behavior and potentially execute arbitrary code or crash the system.

This vulnerability is rated as CRITICAL with a CVSS score of 9.8. It has the potential for significant impact, including arbitrary code execution and system crashes.

Yes, this vulnerability has been reviewed and confirmed by GitHub. The advisory database has also provided additional details and information about the vulnerability.

To fix this vulnerability, you can upgrade to version 0.4.9 or later of the aubio package. Simply run the command pip install --upgrade aubio to update your package.

Related vulnerabilities

Recent vulnerabilities recorded for aubio.

How To Fix

Latest published version: 0.4.9 as of 23 Oct 2026

pip install --upgrade "aubio==0.4.9"

The newest release already contains this fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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