CVE-2026-3910
Google Chromium V8 Improper Restriction of Operations Within the Bounds of a Memory Buffer
- Published13 Mar 2026
- Added to CISA KEV13 Mar 2026
- Remediation due27 Mar 2026
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)
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-3910 being actively exploited?
Yes. CVE-2026-3910 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 13 Mar 2026.
How severe is CVE-2026-3910?
CVE-2026-3910 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 1.03% probability of exploitation.
Which products are affected by CVE-2026-3910?
Affected products include Google Chrome.
How do I fix CVE-2026-3910?
Upgrade affected software to a fixed version, for example Google Chrome 146.0.7680.75 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-3910 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.