VideoLAN libaacs stack memory corruption in path resolution
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Summary
VideoLAN libaacs is affected by a stack buffer overflow in its path-resolving code. A local attacker who gets a crafted symlink with a long target into a disc path, such as through an extracted archive, removable media, or a shared directory, can corrupt stack memory when a user opens it, which may crash the player or potentially allow code execution.
Written by a model
Original description
VideoLAN libaacs 0.7.0 through 0.12.0 on non-macOS, non-Windows builds contains stack-based buffer overflows in aacs_resolve_path() in src/file/path.c from length checks against the wrong buffer. Local attackers can place a symlink with a long target on a disc path a user opens to overflow resolved_path[] and link[], crashing the process or potentially executing code if mitigations are bypassed.
Who should check
Anyone running VideoLAN libaacs 0.7.0 through 0.12.0, such as software that opens disc paths.
“Affecting libaacs >= 0.7.0, <= 0.12.0”
What to do
Check whether your setup matches what the bug needs.
The resolved path walks an attacker-controlled symlinkApply the patch listed under Evidence.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133306 (VideoLAN libaacs 0.7.0 through 0.12.0 Stack Buffer Overflow via aacs_resolve_path()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133306 (entry last updated 2026-11-19):
Affected:
- VideoLAN libaacs: from 0.7.0, through 0.12.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The resolved path walks an attacker-controlled symlink (source: https://code.videolan.org/videolan/libaacs/-/commit/6bbd2143603b785a9382aa8b20d7f328f7c1400e)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-133306 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133306 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://code.videolan.org/videolan/libaacs/-/commit/6bbd2143603b785a9382aa8b20d7f328f7c1400e
- https://code.videolan.org/videolan/libaacs/-/blob/0.12.0/src/file/path.c#L97
- https://code.videolan.org/videolan/libaacs/-/blob/0.12.0/src/file/path.c#L132
- https://code.videolan.org/videolan/libaacs/-/blob/0.12.0/src/file/path.c#L94
- https://code.videolan.org/videolan/libaacs/-/blob/0.12.0/src/file/path.c#L127
- https://code.videolan.org/videolan/libaacs/-/blob/0.12.0/Makefile.am#L51
- https://code.videolan.org/videolan/libaacs
- https://www.vulncheck.com/advisories/videolan-libaacs-0.7.0-through-0.12.0-stack-buffer-overflow-via-aacs-resolve-path
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133306
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133306"}.Affected versions
- VideoLAN libaacsFrom 0.7.0 · through 0.12.0
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 7.3, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 10
| Kind | Source |
|---|---|
| Vendor advisory 7Establishes: Affected and fixed versions. | |
| Patch | code.videolan.org · videolan/libaacs/-/commit/6bbd2143603b785a9382aa8b20d7f328f7c1400e |
| Link | code.videolan.org · videolan/libaacs/-/blob/0.12.0/src/file/path.c#L97 |
| Link | code.videolan.org · videolan/libaacs/-/blob/0.12.0/src/file/path.c#L132 |
| Link | code.videolan.org · videolan/libaacs/-/blob/0.12.0/src/file/path.c#L94 |
| Link | code.videolan.org · videolan/libaacs/-/blob/0.12.0/src/file/path.c#L127 |
| Link | code.videolan.org · videolan/libaacs/-/blob/0.12.0/Makefile.am#L51 |
| Link | code.videolan.org · videolan/libaacs |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133306 |
| Record | NVD · CVE-2026-133306 |
| Other links 1 | |
| Link | vulncheck.com · advisories/videolan-libaacs-0.7.0-through-0.12.0-stack-buffer-overflow-via-aacs-resolve-path |
Questions about CVE-2026-133306
Is CVE-2026-133306 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A stack buffer overflow in aacs_resolve_path() can corrupt stack memory and crash the player, and it could potentially execute code. It occurs when the resolved path walks an attacker-controlled symlink.
Source: code.videolan.org, vulncheck.com
Which versions are affected by CVE-2026-133306?
libaacs: from 0.7.0 through 0.12.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions of VideoLAN libaacs from 0.7.0 through 0.12.0 are in the reported range. The bug needs a resolved path that walks an attacker-controlled symlink. To check a installed version, look at the libaacs version reported by your package manager or build configuration.
Source: code.videolan.org, vulncheck.com
How do I fix CVE-2026-133306?
The checked facts do not name a fixed version or vendor patch, so no upgrade target can be given from them. Check the VideoLAN libaacs project or advisory for a fixed release.
Source: code.videolan.org, vulncheck.com
Related
- CVE-2026-102875VLC media player before 3.0.24 Path Traversal via skins2
- CVE-2017-8311Potential heap based buffer overflow in ParseJSS in VideoLAN VLC before 2.2.5 due to skipping NULL terminator in an input string allows…
- CVE-2026-56711VLC media player 3.0.0 through 3.0.23 memory corruption vulnerability
- CVE-2026-112283libbluray through 1.5.1 Uncontrolled Memory Allocation via _parse_extent_start_points
- CVE-2026-112282VideoLAN libbluray through 1.5.1 Out-of-Bounds Read via clpi_access_point
- CVE-2026-112058libdvdnav through 7.0.0 Out-of-Bounds Read via set_PTT JumpTT
No corrections so far. Something wrong on this page? Report an error.