What is CVE-2026-3910?
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)
The record classifies CVE-2026-3910 under weakness classes CWE-94, CWE-119. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 4 affected-product entries are recorded, across 4 vendors, listed below. The identifier was first published 229 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 1.0% probability of exploitation in the next 30 days, higher than 63.7% of all scored CVEs
- CISA KEV
- Listed since 2026-03-13, federal remediation deadline 2026-03-27
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2026-03-13, last modified 2026-03-14
Is CVE-2026-3910 being exploited?
CISA added CVE-2026-3910 to the Known Exploited Vulnerabilities catalog on 2026-03-13, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-03-27 under BOD 22-01. Weaponised exploit code for CVE-2026-3910 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 44 in the Threadlinqs vulnerability feed.
- 5o1z/CVE-2026-3910 (github)
Affected products and versions
How to fix CVE-2026-3910
The record marks a vendor fix as available for CVE-2026-3910. Vendor advisory: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_12.html. Because CVE-2026-3910 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-03-27. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-3910
3 tracked threats in the Threadlinqs corpus reference CVE-2026-3910, either in the campaign’s CVE list or as an indicator on the campaign record.
- Google Chrome V8 Out-of-Bounds Read/Write Zero-Day CVE-2026-11645 Exploited in the Wild — HIGH · 2026-06-09
- Google Chrome Double Zero-Day — Skia OOB Write & V8 Implementation Flaw (CVE-2026-3909, CVE-2026-3910) — CRITICAL · 2026-03-15
- Chrome V8 and Skia Zero-Days Under Active Exploitation (CVE-2026-3910, CVE-2026-3909) — CRITICAL · 2026-03-13
Sources
Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .