Quick answers
- Is CVE-2026-95127 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-95127 being exploited in the wild.
- How severe is CVE-2026-95127?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- Libass 0.17.5.
- Is there a fix for CVE-2026-95127?
- A patch was published on 2026: Fix available in GitHub PR #955 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-95127 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-95127?
- 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.
Technical details
A signed integer overflow (CWE-190) occurs in the ass_outline_construct() function when processing attacker-controlled subtitle parameters such as script resolution, font size, margins, or layout values. The bounding-box subtraction (bbox.x_max - bbox.x_min or bbox.y_max - bbox.y_min) overflows a signed 32-bit integer, causing undefined behavior and a crash. The vulnerability is reachable remotely through normal subtitle rendering without requiring special preconditions.
Affected products
- libass libass 0.17.5
Timeline
- 2026-10-10: disclosed: GitHub issue #947 disclosed
- 2026-10-13: advisory: NVD published
- 2026: patched: Fix available in GitHub PR #955