Critical Vulnerability in Chromium Package: CVE-2026-95368

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95368: ... 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 developed by Google, known for its speed, simplicity, and security features. It serves as the foundation for several other browsers, including Google Chrome. The package is widely used across various operating systems, including Debian. This vulnerability, identified as CVE-2026-95368, affects multiple versions of the Chromium package in Debian distributions, potentially exposing users to security risks.

Vulnerability Detail

CVE-2026-95368 is a security vulnerability that arises from improper handling of certain inputs within the Chromium browser. This flaw could allow an attacker to execute arbitrary code or cause a denial of service, leading to potential data breaches or system compromises. The vulnerability is present in all versions of the Chromium package starting from its inception, making it critical 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 measure, users can disable JavaScript in the Chromium settings to mitigate the risk of exploitation until an update is applied. This can be done by navigating to Settings > Privacy and Security > Site Settings > JavaScript and toggling the option to 'Blocked'.

Conclusion

CVE-2026-95368 represents a significant security risk for users of the Chromium package in Debian distributions. It is crucial to update to the latest version to mitigate potential threats. Users are encouraged to monitor their applications for vulnerabilities using tools like Vulert, which can provide real-time alerts without requiring extensive setup.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95368 is a critical vulnerability in the Chromium package that could allow attackers to execute arbitrary code or cause a denial of service.

All versions of the Chromium package starting from its initial release in Debian distributions are affected by this vulnerability.

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

If an immediate update is not possible, consider disabling JavaScript in the browser settings as a temporary workaround.

More details can be found in the official vulnerability database or through the Debian security advisories.

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