Read the docs
TI-2026-83144 Aliases CVE-2026-61626

Out-of-bounds bit clears in libass via negative Matroska ReadOrder

Priority LOW 31CWE-787Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Passive
Attack complexity
High
Attack requirements
None
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-787 and the CVSS impact.

Summary

libass from 0.17.4 before 0.17.5 does not guard negative Matroska ReadOrder values during event pruning. The out-of-bounds write (CWE-787) lets an attacker clear bits to zero at attacker-controlled positions near the NULL pointer. An attacker needs a user to load a malicious Matroska stream and later prune its events, and the expected result is denial of service.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

Description from the CNA

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.

Why it matters now

EPSS 0.00118 1st percentileScored 2026-11-07
Fix Fixed libass (libass): 0.17.5

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
libasslibass0.17.4 to before 0.17.50.17.5Patch availableCNA
  • libass Vendorlibass Affected 0.17.4 to before 0.17.5 Fixed in 0.17.5 Patch available CNA

Remediation

Update libass to version 0.17.5, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-31

  • Fix · CNA libass (libass) Fixed in 0.17.5

Vendor assessments

Red Hat

Red Hat's page for this CVE →

Not affected: 1 product
  • Red Hat

Timeline

  1. 2026-10-30 Threatist record created from CVE-2026-61626
  2. 2026-10-31 Affected versions changed · Red Hat
  3. 2026-10-31 CVSS score added · Red Hat
  4. 2026-11-01 Priority changed: MEDIUM → LOW

References

  • TI-2026-83145 Out-of-bounds read and write in libass wrap_lines_measure CVSS 4.0HIGH 7.3

Sources