Quick answers
- Is CVE-2026-61627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61627 being exploited in the wild.
- How severe is CVE-2026-61627?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Libass before 0.17.5.
- Is there a fix for CVE-2026-61627?
- Yes: fixed in 0.17.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61627 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61627?
- Check whether you run Libass at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.17.5
Technical details
The vulnerability exists in the wrap_lines_measure function where a final line consisting entirely of skippable characters (spaces or literal \n sequences) in wrap modes other than two can cause the line-measurement loop to overshoot the glyph array by one entry. If total text size exactly matches the allocated glyph-array capacity, this causes an uninitialized 32-bit read followed by out-of-bounds writes of pos.x and pos.y values. Attack requires processing a malicious ASS/SSA subtitle file; practical exploitation is constrained by limited writes and ASLR defenses.
Affected products
- libass libass before 0.17.5
Timeline
- 2026-10-30: disclosed
- 2026-06-24: patched: version 0.17.5 released