Heap Buffer Overflow Vulnerability in libxaac: Critical Security Flaw Detected

libxaac Updated 08 Jul 2026

Summary

15/06/2026
HIGH
Yes i
High
Not published

OSV-2026-917: Heap-buffer-overflow in ixheaace_process. Affects libxaac versions >= fb6a68848a05401a1aba5747d29595cd344faa40, < b9193197055e1e87f841f73c1a3fbca796b2da09. Fixed in b9193197055e1e87f841f73c1a3fbca796b2da09. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libxaac is an open-source audio codec library designed for encoding and decoding AAC audio streams. It is widely used in various multimedia applications due to its efficiency and quality. However, like many software libraries, it is susceptible to vulnerabilities that can compromise the integrity and security of applications that depend on it. The recent discovery of a heap buffer overflow in the ixheaace_process function poses a significant risk, potentially allowing attackers to exploit this flaw for malicious purposes.

Vulnerability Detail

The vulnerability identified is a heap buffer overflow occurring in the ixheaace_process function of the libxaac library. This issue was reported through OSS-Fuzz, indicating that it can lead to unauthorized memory writes, potentially crashing the application or allowing an attacker to execute arbitrary code. The flaw was introduced in commit fb6a68848a05401a1aba5747d29595cd344faa40 and has been fixed in commit b9193197055e1e87f841f73c1a3fbca796b2da09. The severity of this vulnerability is classified as HIGH, making it critical for users to address it promptly.

How To Fix

Minimum fixed version

b9193197055e1e87f841f73c1a3fbca796b2da09

This is the first release that contains the fix.

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

Workaround

As a temporary workaround, users are advised to avoid using the ixheaace_process function until the library has been updated to the patched version. Additionally, implementing input validation and sanitization can help mitigate the risk of exploitation until a proper fix is applied.

Conclusion

The heap buffer overflow vulnerability in the libxaac library poses a significant risk to applications that utilize this codec. It is crucial for developers and users to update to the patched version to mitigate potential security threats. Utilizing tools like Vulert can help monitor for vulnerabilities and ensure the safety of your software.

See every vulnerability recorded for libxaac →

Share this vulnerability

FAQ

A heap buffer overflow occurs when a program writes more data to a buffer located on the heap than it can hold, potentially overwriting adjacent memory and leading to unpredictable behavior or security vulnerabilities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By utilizing the Vulert playground, you can check if your application is affected without requiring any installation or signup.

If exploited, this vulnerability could allow attackers to crash the application or execute arbitrary code, leading to data breaches or unauthorized access to sensitive information.

Yes, you should upgrade to the fixed version of libxaac, which is identified by commit b9193197055e1e87f841f73c1a3fbca796b2da09.

If an immediate update is not possible, refrain from using the ixheaace_process function and implement input validation to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for libxaac.

How To Fix

Minimum fixed version

b9193197055e1e87f841f73c1a3fbca796b2da09

This is the first release that contains the 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