Critical Vulnerability in Chromium Package: CVE-2026-95293

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95293: ... 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 Penetration testing for web, API and mobile 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 many popular browsers, including Google Chrome. The package is widely used across various 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-95293 is a critical vulnerability identified in the Chromium package that allows for potential exploitation. The vulnerability originates from a flaw in the browser's handling of specific web content, which could lead to unauthorized access or manipulation of user data. If exploited, this vulnerability could allow attackers to execute arbitrary code, leading to severe consequences such as data breaches or system compromise.

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 mitigate the risk of exploitation until a patch is applied. This can be done by navigating to Settings > Privacy and Security > Site Settings > JavaScript and toggling the setting to 'Blocked'.

Conclusion

CVE-2026-95293 poses a significant risk to users of the Chromium package. It is crucial to stay informed about vulnerabilities and apply necessary updates promptly. Utilizing tools like Vulert can help monitor and alert for open-source vulnerabilities in your software.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

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

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

The risks include unauthorized access to user data, potential data breaches, and system compromise.

You can update the Chromium package by running 'sudo apt update && sudo apt upgrade chromium' in your terminal.

Yes, you can disable JavaScript in your browser settings as a temporary workaround.

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