Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2026-3909

Google Skia Out-of-Bounds Write Vulnerability

Google Skia

Out of bounds write in Skia in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
2.3%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
13 Mar 2026
CWE-787

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 13 March 2026. US federal agencies were required to remediate it by 27 March 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 2.3%, which is higher than 83.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2026-3909 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2026-3909.

What does CVE-2026-3909 affect?

CVE-2026-3909 affects Google Skia. Out of bounds write in Skia in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2026-3909?

CVE-2026-3909 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 2.3%, higher than 83.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 27 March 2026.

How should organisations respond to CVE-2026-3909?

Apply the vendor patch for Google Skia as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.