Critical Vulnerability in Chromium Package Affecting Debian Versions 12, 13, and 14

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95292: ... 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 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

Chromium is an open-source web browser project that aims to build a safer, faster, and more stable way for all users to experience the web. It serves as the foundation for several browsers, including Google Chrome. The vulnerability in question affects multiple Debian distributions, specifically versions 12 (Bookworm), 13 (Trixie), and 14 (Forky), potentially exposing users to security risks.

Vulnerability Detail

The vulnerability identified as CVE-2026-95292 arises from a flaw in the Chromium package that could allow attackers to exploit the browser's functionalities. This could lead to unauthorized access or manipulation of user data, posing significant risks to user privacy and security. The issue has been introduced in all versions of the affected package, and its ramifications could be severe, especially for users handling sensitive information.

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 advised to monitor for updates and apply them as soon as they become available.

Conclusion

The CVE-2026-95292 vulnerability in the Chromium package poses significant risks to users of Debian versions 12, 13, and 14. It is essential to update the package to the latest version to safeguard against potential exploits. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95292 is a vulnerability in the Chromium package that affects multiple Debian distributions, potentially allowing unauthorized access to user data.

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

While no specific workarounds are available, it is crucial to monitor for updates and apply them as soon as possible to mitigate risks.

Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

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