CVE-2026-3910: Google Chromium V8 Improper Restriction of Operations Within the Bounds of a Memory Buffer
Google Chromium V8 · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-13.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 3.0%
- higher than 87.6% of all CVEs
- Added to CISA KEV
- 2026-03-13
- US federal due date 2026-03-27
- Ubuntu priority
- –
CVE-2026-3910 explained
CVE-2026-3910 is an inappropriate implementation flaw in the V8 JavaScript engine of Google Chrome before 146.0.7680.75. A remote attacker can run arbitrary code inside the browser sandbox through a crafted HTML page. It is listed in the CISA Known Exploited Vulnerabilities catalog, so systems running Chromium should be updated promptly.
Impact
An attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the Chromium sandbox. No privileges are needed and the attack works over the network with low complexity, but user interaction is required. A successful attack can have high impact on confidentiality, integrity and availability within the affected scope. CISA lists the flaw as known to be exploited.
Who is affected
On Debian, the chromium source package is affected. Fixed versions exist for all listed releases: Debian 12 (bookworm) in 146.0.7680.80-1~deb12u1, Debian 13 (trixie) in 146.0.7680.80-1~deb13u1, and Debian 14 (forky), the testing distribution, in 146.0.7680.80-1. All fixes are in the standard archive. The facts list no Ubuntu releases.
Written with AI from the data on this page and checked against it automatically.
Official description
Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 146.0.7680.75
- 146.0.7680.75
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Debian 14 (forky)·chromium
testing distribution
Fixed: 146.0.7680.80-1
Debian 13 (trixie)·chromium
Fixed: 146.0.7680.80-1~deb13u1
Debian 12 (bookworm)·chromium
Fixed: 146.0.7680.80-1~deb12u1
What to do
- Update the
chromiumpackage to the fixed version for your Debian release. - On Debian 12 (bookworm), install
146.0.7680.80-1~deb12u1or later. - On Debian 13 (trixie), install
146.0.7680.80-1~deb13u1or later; on Debian 14 (forky),146.0.7680.80-1or later. - Close and restart all running Chromium instances so the updated code is loaded.
- Check that no hosts still run older Chromium builds, and follow the Debian security advisory.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above.
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'2. Compare each installed version with the fixed version for your release from the table
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
Questions about CVE-2026-3910
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-3910 to its Known Exploited Vulnerabilities catalog on 2026-03-13, with a US federal due date of 2026-03-27. Whether it is used in ransomware campaigns is listed as unknown.
- Do I need to restart anything after updating?
- Yes. Running Chromium processes keep using the old code until they are closed. Restart the browser after installing the updated
chromiumpackage. - Can an attacker compromise the system without user action?
- No. User interaction is required: a user must open a crafted HTML page. The code then runs inside the browser sandbox.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.