Critical Vulnerability in Chromium Package - CVE-2026-95327

chromium Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-95327: ... 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 browsers, including Google Chrome. The vulnerability identified as CVE-2026-95327 affects multiple Debian distributions, including Debian 12 (Bookworm), Debian 13 (Trixie), and Debian 14 (Forky), potentially compromising user security and privacy.

Vulnerability Detail

CVE-2026-95327 is a critical vulnerability that arises from improper handling of certain web content, which could allow an attacker to execute arbitrary code or perform unauthorized actions on behalf of the user. This vulnerability is particularly concerning as it affects multiple versions of the Chromium package across different Debian distributions, making a wide range of systems susceptible to exploitation. The origin of this vulnerability lies in the core rendering engine of Chromium, which fails to adequately validate input data, leading to potential security breaches.

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 the browser settings, selecting 'Privacy and Security', and then adjusting the JavaScript settings accordingly.

Conclusion

CVE-2026-95327 represents a significant security risk for users of the Chromium package across multiple Debian distributions. It is crucial for users to update their systems 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-95327 is a critical vulnerability in the Chromium package that could allow attackers to execute arbitrary code.

Debian 12 (Bookworm), Debian 13 (Trixie), and Debian 14 (Forky) are all 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 immediate updating is not possible, consider disabling JavaScript as a temporary workaround to reduce the risk of exploitation.

More detailed information can be found in the official Debian security advisories and the 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