Critical Vulnerability in Chromium Package: CVE-2026-95329

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95329: ... 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

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 in various operating systems, including Debian. However, recent findings have identified a critical vulnerability (CVE-2026-95329) that affects multiple versions of the Chromium package across different Debian distributions, potentially compromising user security.

Vulnerability Detail

CVE-2026-95329 is a security vulnerability that allows unauthorized access to sensitive user data through the Chromium browser. The vulnerability originates from improper handling of certain web requests, which can be exploited by malicious actors to execute arbitrary code or access confidential information. The ramifications of this vulnerability are severe, as it can lead to data breaches, loss of user privacy, and exploitation of system resources.

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 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 option off.

Conclusion

CVE-2026-95329 represents a significant security risk for users of the Chromium package across various Debian distributions. It is crucial for users to update their packages promptly to mitigate potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for chromium →

Share this vulnerability

FAQ

CVE-2026-95329 is a critical vulnerability found in the Chromium package that can lead to unauthorized access to user data.

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 workaround, you can disable JavaScript in your browser settings to reduce the risk of exploitation.

Yes, CVE-2026-95329 affects multiple versions of the Chromium package across different Debian distributions.

Detailed information about CVE-2026-95329 can be found in the Debian security advisories and on the official CVE database.

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