Critical Vulnerability in Chromium Packages Across Debian Distributions

chromium Updated 22 Oct 2026

Summary

23/09/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-95328: ... Affects chromium versions 113.0.5672.126-1 – 153.0.8010.52-1~deb13u1. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Chromium is an open-source web browser developed by Google, known for its speed, simplicity, and security features. It serves as the foundation for various browsers, including Google Chrome. The package is widely used in Debian distributions, including Bookworm, Trixie, and Forky. However, recent findings have identified a vulnerability that affects all versions of Chromium in these distributions, posing significant risks to users.

Vulnerability Detail

The vulnerability identified as CVE-2026-95328 affects Chromium packages in Debian distributions. It originates from a flaw in the browser's handling of specific web content, which could allow an attacker to execute arbitrary code or cause a denial of service. This vulnerability can lead to severe ramifications, including data breaches, unauthorized access to user information, and potential system compromise. Users are strongly advised to address this issue promptly to mitigate risks.

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 of now, no specific workarounds have been provided for this vulnerability. Users are encouraged to apply the update as soon as it becomes available to ensure their systems remain secure.

Conclusion

CVE-2026-95328 represents a significant security risk for users of Chromium in various Debian distributions. It is essential to stay informed about such vulnerabilities and apply updates promptly to safeguard your system. Utilizing tools like Vulert can help monitor and alert you to potential vulnerabilities in your software.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95328 is a critical vulnerability affecting Chromium packages in Debian distributions, allowing potential arbitrary code execution.

The affected distributions include Debian 12 (Bookworm), Debian 13 (Trixie), and Debian 14 (Forky).

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.

While no specific workarounds are available, it is crucial to update Chromium as soon as possible to mitigate risks associated with this vulnerability.

It is recommended to check for updates regularly, ideally weekly, to ensure your software is protected against known vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for chromium.

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