Application crash via unchecked Matroska element read
Published Jan 8, 2021 · Updated Jul 9, 2026
Heap-buffer over-read in VideoLAN VLC media player 3.0.11 and earlier allows attackers to crash VLC via a crafted MKV file. During Matroska track parsing, EbmlTypeDispatcher::send reads eight bytes from a two-byte heap allocation without validating the element's available size. Opening or preparsing the file is required; the demonstrated consequence is process termination, while an Arch advisory classifies the flaw as arbitrary code execution.
Summary
What happened
Heap-buffer over-read in VideoLAN VLC media player 3.0.11 and earlier allows attackers to crash VLC via a crafted MKV file. During Matroska track parsing, EbmlTypeDispatcher::send reads eight bytes from a two-byte heap allocation without validating the element's available size. Opening or preparsing the file is required; the demonstrated consequence is process termination, while an Arch advisory classifies the flaw as arbitrary code execution.
The record
- CVE
- CVE-2020-26664
- Published
- Jan 8, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 8, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo