Skip to content
Fencer Intel
high 8.8

CVE-2020-26682 json

In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.

published 6y ago modified 3mo ago also EUVD-2020-19224 , JLSEC-2026-155

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.8%
EPSS 1.8% chance of exploitation in 30 days, percentile 78%
public exploits
0
none known

Summary

In libass 0.14.0, the `ass_outline_construct`'s call to `outline_stroke` causes a signed integer overflow.

Patch / fix

  • julia libass_jll 0.15.1+0
  • libass Debian 14, Debian 13, Debian 12 1:0.15.0-1

debian advisories DEBIAN-CVE-2020-26682

  • libass Ubuntu Pro 18.04 LTS 1:0.14.0-1ubuntu0.1~esm1
  • libass Ubuntu Pro 20.04 LTS 1:0.14.0-2ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2020-26682

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libass SLES for SAP 15 SP1, SLES for SAP 15, SLES 15-LTSS +11 more 0.14.0-3.3.1

suse advisories SUSE-SU-2021:0936-1

  • libass openSUSE Leap 15.2 0.14.0-lp152.4.3.1

opensuse advisories openSUSE-SU-2021:0472-1

  • libass Arch Linux 0.15.0-1

arch linux advisories AVG-1285

Is CVE-2020-26682 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-26682 updated cvss 6.2

libass: in`ass_outline_construct`'s call to `outline_stroke` a signed integer overflow could result in undefined behaviour

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.80% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/libass/libass/issues/431 referenced PoC, tagged "exploit" by a source, unverified
  • openwall.com http://www.openwall.com/lists/oss-security/2020/11/19/7 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
julia libass_jll
<0.15.1+0
0.15.1+0

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.