Skip to content
High-Risk CVE-2026-133306 in VideoLAN Libaacs Library

High-Risk CVE-2026-133306 in VideoLAN Libaacs Library

First seen 20 Nov 2026, 01:45 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 20, 2026 at 01:47 UTC
  • •CVE-2026-133306 affects VideoLAN libaacs versions 0.7.0 to 0.12.0.
  • •Exploitation requires local access to place a malicious symlink.
  • •No active exploitation has been reported as of now.

A stack-based buffer overflow vulnerability (CVE-2026-133306) has been identified in VideoLAN's libaacs versions 0.7.0 through 0.12.0, affecting non-macOS and non-Windows systems. The flaw arises from improper length checks in the aacs_resolve_path() function, allowing local attackers to exploit it by placing a crafted symlink. Successful exploitation could lead to process crashes or arbitrary code execution, although no active exploitation has been reported. The vulnerability is characterized as high-impact but constrained, requiring local access for attack. Users of Blu-ray playback software or applications that bundle this library are particularly at risk. Mitigation involves upgrading to a patched version and avoiding untrusted media until a fix is applied. The CVE was published on November 19, 2026, with a CVSS score of 7.3.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-19
CVE-2026-133306 published
The vulnerability was officially disclosed with a CVSS score of 7.3, indicating a high severity.
Redpacketsecurity

More articles in this cluster (2)

Following this threat?

Track CVE-2026-133306 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which systems are affected?
Linux and other non-macOS, non-Windows systems using libaacs versions 0.7.0 to 0.12.0 are affected.
What should I do to mitigate this vulnerability?
Upgrade to a patched version of libaacs and avoid opening untrusted discs until a fix is applied.
Is there any evidence of exploitation in the wild?
No active exploitation has been reported, and the vulnerability is currently characterized as constrained.