Critical Vulnerability in Chromium Package - CVE-2026-95299

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95299: ... 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 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 package is widely used across various operating systems, including Debian. This vulnerability affects multiple versions of the Chromium package in Debian distributions, making it crucial for users to be aware of its implications.

Vulnerability Detail

CVE-2026-95299 is a critical vulnerability identified in the Chromium package that could potentially allow attackers to exploit the browser's functionality. The vulnerability originates from improper handling of certain inputs, which may lead to arbitrary code execution or data leakage. If exploited, this could compromise user data and system integrity, making it imperative for users to address this issue promptly.

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 disable certain features of the Chromium browser that may be exploited until a patch is applied. This can be done by launching Chromium with the following command: 'chromium --disable-features=FeatureName', replacing 'FeatureName' with the specific feature that is suspected to be vulnerable.

Conclusion

CVE-2026-95299 poses a significant risk to users of the Chromium package in Debian distributions. It is essential to stay informed about such vulnerabilities and take immediate action to update or mitigate risks. Utilizing tools like Vulert can help monitor and alert for open-source vulnerabilities effectively.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95299 is a critical vulnerability in the Chromium package that could allow attackers to execute arbitrary code or leak sensitive information.

The vulnerability affects Chromium packages in Debian distributions 12 (bookworm), 13 (trixie), and 14 (forky).

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If an immediate update is not possible, consider disabling vulnerable features as a temporary workaround until the patch can be applied.

More information can be found in the official CVE database or through the Debian security advisories related to CVE-2026-95299.

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