# CVE-2020-26682: Integer overflow in n/a

> A signed integer overflow in libass can lead to a denial of service when processing malicious subtitle files.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-26682, GHSA-87rf-m79q-qqqf, JLSEC-2026-155, MGASA-2021-0017, SUSE-SU-2021:0936-1, UBUNTU-CVE-2020-26682, openSUSE-SU-2021:0472-1

## What is CVE-2020-26682?

CVE-2020-26682 is a high-severity vulnerability in n/a, published on 16 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2020-26682?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libass` | SUSE:Enterprise Storage 6 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Server 15 SP1-BCL | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Manager Proxy 4.0 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Manager Retail Branch Server 4.0 | All versions | 0.14.0-3.3.1 |
| `libass` | SUSE:Manager Server 4.0 | All versions | 0.14.0-3.3.1 |
| `libass` | openSUSE:Leap 15.2 | All versions | 0.14.0-lp152.4.3.1 |

Products: Libass Project Libass.

## How do I fix CVE-2020-26682?

Upgrade to a fixed version.

## Is CVE-2020-26682 being exploited?

There is no known exploitation of CVE-2020-26682 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-24994](https://insights.sbomify.com/CVE-2020-24994/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26682 and fix it if it is affected.

What it is: CVE-2020-26682 is a high-severity vulnerability in n/a, published on 16 Oct 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-26682 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26682/ (Markdown: https://insights.sbomify.com/CVE-2020-26682/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26682
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26682
- OSV: https://osv.dev/vulnerability/CVE-2020-26682

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26682/
Summaries are generated and may contain mistakes; the official description above is the record.