CVE-2026-133306 in libaacsinfo

Summary

by MITRE • 11/20/2026

VideoLAN libaacs 0.7.0 through 0.12.0 contains a stack-based buffer overflow vulnerability in aacs_resolve_path() that allows local attackers to corrupt stack memory via crafted symlinks in disc paths. Attackers can plant a symlink with a long target in an extracted archive, removable media or shared directory, so that strcat() overflows the 1024-byte link buffer when opened, crashing the player or potentially executing code.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Analysis

by VulDB Data Team • 11/20/2026

The vulnerability identified within VideoLAN libaacs versions ranging from 0.7.0 through 0.12.0 represents a critical stack-based buffer overflow located specifically in the aacs_resolve_path function. This flaw arises from improper handling of file system paths when resolving AACS protected media, allowing local attackers to corrupt memory on the application's call stack. The root cause lies in the use of strcat() for string concatenation without adequate bounds checking against the fixed-size 1024-byte buffer allocated for link targets. When an attacker constructs a malicious symlink with a target path that exceeds this limit, the function writes beyond the boundaries of the allocated memory space, leading to stack corruption and potential arbitrary code execution or denial of service conditions.

From a technical perspective, the exploitation vector relies on the manipulation of symbolic links within directories accessed by the media player application. An attacker can plant a symlink with an excessively long target string in locations such as extracted archives, removable media like USB drives, or shared network directories that are subsequently opened by libaacs. Upon opening these paths, the library attempts to resolve and concatenate path components using strcat(), which does not perform length validation before appending data to the destination buffer. This lack of input sanitization allows the crafted symlink target to overflow the static 1024-byte array residing on the stack, overwriting adjacent memory including return addresses or function pointers stored in higher stack frames.

The operational impact of this vulnerability is significant for users relying on libaacs for playing protected Blu-ray discs or media files containing AACS encryption headers. Successful exploitation can result in a crash of the host application due to segmentation faults caused by corrupted stack memory, leading to denial of service. More critically, if specific conditions are met such as executable stack permissions and predictable memory layouts, an attacker could leverage this overflow to execute arbitrary code with the privileges of the user running the media player. This poses a severe risk in environments where users frequently open untrusted removable media or download archives from unreliable sources, as it provides a pathway for local privilege escalation or remote code execution if combined with other vulnerabilities.

This vulnerability aligns with CWE-121, which classifies stack-based buffer overflow errors resulting from insufficient bounds checking during memory operations. It also relates to CWE-670 regarding the use of functions that are inherently prone to buffer overflows without proper validation. In terms of attack tactics, this scenario reflects ATT&CK technique T1548.002, Abuse Elevation Control Mechanism, specifically through local privilege escalation via stack corruption if exploited in a context where higher privileges can be gained. Additionally, the reliance on crafted symlinks touches upon CWE-59 Improper Link Resolution Before File Access, highlighting the need for secure path resolution practices that validate and sanitize all input paths before processing them within sensitive functions.

Mitigation strategies primarily involve upgrading to patched versions of libaacs where this issue has been resolved through improved buffer management and strict length validation prior to string concatenation operations. Developers should ensure that any function handling file system paths implements rigorous bounds checking, preferably using safer alternatives like strncat or snprintf with explicit size limits derived from the destination buffer capacity. For end-users, it is advisable to exercise caution when opening media files or archives obtained from untrusted sources and to keep all multimedia playback software updated to the latest stable release containing security patches for known vulnerabilities in underlying libraries such as libaacs.

Responsible

VulnCheck

Reservation

11/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00173

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!