Critical Vulnerability in Chromium Package: CVE-2026-95302

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95302: ... 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 various browsers, including Google Chrome. The package is widely used across different operating systems and is known for its speed and security features. However, it is susceptible to vulnerabilities that can compromise user data and system integrity.

Vulnerability Detail

CVE-2026-95302 is a critical vulnerability affecting the Chromium package across multiple Debian distributions. This vulnerability originates from a flaw in the browser's handling of certain web content, which could allow an attacker to execute arbitrary code, leading to potential data breaches or system compromise. The vulnerability has been introduced in all versions of the affected packages, making it imperative for users to address it 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 JavaScript in their browser settings to reduce the risk of exploitation until a patch is applied. This can be done by navigating to the browser settings, selecting 'Privacy and security', and then 'Site settings' to adjust JavaScript permissions.

Conclusion

CVE-2026-95302 poses a significant threat to users of the Chromium package across various Debian distributions. It is crucial for users to update their systems promptly to the latest patched version to mitigate the risks associated with this vulnerability. Temporary workarounds, such as disabling JavaScript, can provide limited protection until a full update is applied.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95302 is a critical vulnerability in the Chromium package that could allow attackers to execute arbitrary code.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

As a temporary measure, consider disabling JavaScript in your browser settings to minimize the risk of exploitation.

Yes, a patched version of the Chromium package is available. Users should update to the latest version to ensure their systems are secure.

Failure to address CVE-2026-95302 could lead to unauthorized access to sensitive data, system compromise, and other security 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