Threat Intelligence / CVE / CVE-2026-3910

CVE-2026-3910 — Google Chrome

CISA KEV

CVSS v3.1 8.8 (HIGH) · EPSS 0.6% (higher than 69.7% of all scored CVEs) · Priority 9/10 · Published 2026-03-13

As of 2026-03-13, CVE-2026-3910 is a HIGH-severity vulnerability in Google Chrome, CVSS v3.1 8.8, EPSS 0.6% (69.7th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-13), with a US federal remediation deadline of 2026-03-27. Threadlinqs Intelligence links 3 tracked threat campaigns to CVE-2026-3910, most recently “Google Chrome V8 Out-of-Bounds Read/Write Zero-Day CVE-2026-11645 Exploited in the Wild”.

Last updated: 2026-03-13

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 184 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): 0.6% probability of exploitation in the next 30 days, higher than 69.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

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. It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

Affected products and versions

Google: Chrome
Apple: Macos
Linux: Kernel
Microsoft: Windows

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

Seeded from threadlinqs-intel and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.

Full detection coverage & IOCs for threats exploiting CVE-2026-3910 are available via the Threadlinqs MCP server (Purple tier). View plans →

← all vulnerabilities · Markdown version · Threadlinqs Intelligence