Critical Vulnerability in libass Package: CVE-2026-61627

libass Updated 22 Oct 2026

Summary

14/07/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-61627: ... Affects libass versions 1:0.15.0-2 – 1:0.17.5-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libass is a portable subtitle renderer for ASS (Advanced SubStation Alpha) and SSA (SubStation Alpha) formats. It is widely used in multimedia applications to provide subtitle support. The package is essential for applications that require advanced subtitle rendering capabilities, making it a critical component in many media players and processing tools. However, vulnerabilities in libass can lead to severe security risks, including potential code execution and data breaches.

Vulnerability Detail

CVE-2026-61627 is a vulnerability identified in the libass package that allows for potential exploitation due to improper handling of input data. This vulnerability can lead to arbitrary code execution, which may compromise the integrity and confidentiality of the system. The issue arises from a flaw in the way libass processes subtitle files, making it susceptible to crafted input that can trigger unexpected behavior. Attackers could exploit this vulnerability to execute malicious code on affected systems, leading to severe consequences.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can avoid using the affected features of libass until the package is updated. Additionally, users can limit the exposure of their systems by restricting access to applications that utilize libass for subtitle rendering.

Conclusion

CVE-2026-61627 represents a significant security risk for users of the libass package. It is crucial to update to the latest patched versions to mitigate potential threats. Users should remain vigilant and utilize tools like Vulert to monitor for vulnerabilities in their software.

See every vulnerability recorded for libass →

Share this vulnerability

FAQ

CVE-2026-61627 is a vulnerability in the libass package that can lead to arbitrary code execution due to improper input handling.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

As a temporary measure, avoid using features of libass that may be vulnerable and restrict access to applications that rely on it.

Failing to address CVE-2026-61627 can lead to unauthorized code execution, data breaches, and potential system compromise.

Detailed information can be found in the Debian security advisories and on the official CVE database.

Related vulnerabilities

Recent vulnerabilities recorded for libass.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback