libass: Out-of-bounds bit clears for negative Matroska ReadOrder values
Impact
libass is a portable subtitle renderer for the ASS/SSA (Advanced Substation Alpha/Substation Alpha) subtitle format. From 0.17.4 until 0.17.5, libass event pruning does not guard negative Matroska ReadOrder values, allowing an attacker to clear arbitrarily many bits to zero at attacker-controlled positions near the NULL pointer. Exploitation requires a malicious Matroska stream loaded through ass_process_chunk, enabled read-order checking, and later pruning of the malicious events. Read-order checking is enabled by default unless ass_set_check_readorder is called with zero; pruning must…
Source excerpt · GitHub_MExploitation requires a malicious Matroska stream loaded through ass_process_chunk, enabled read-order checking, and later pruning of the malicious events.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
libass · GitHub_M
libass
1 range
libass · GitHub_M
libass
Compare with this publisher’s ranges. This does not inspect your installation.
affected
>= 0.17.4, < 0.17.5
Other versions: unknown
Original source description
libass is a portable subtitle renderer for the ASS/SSA (Advanced Substation Alpha/Substation Alpha) subtitle format. From 0.17.4 until 0.17.5, libass event pruning does not guard negative Matroska ReadOrder values, allowing an attacker to clear arbitrarily many bits to zero at attacker-controlled positions near the NULL pointer. Exploitation requires a malicious Matroska stream loaded through ass_process_chunk, enabled read-order checking, and later pruning of the malicious events. Read-order checking is enabled by default unless ass_set_check_readorder is called with zero; pruning must occur explicitly through ass_prune_events or through automatic pruning previously enabled with ass_configure_prune. On common systems with arithmetic right shift, 32-bit int values, the upper address region reserved to the kernel, and matching binary/kernel architecture, the expected consequence is denial of service. More extensive exploitation on uncommon systems is theoretical and strongly constrained by the target addresses, bit-clearing-only mutation, and ASLR. This issue is fixed in version 0.17.5.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-61626View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.