CVE-2026-3909: Google Skia Out-of-Bounds Write Vulnerability

Published Mar 12, 2026
·
Updated

Chromium: CVE-2026-3909 Out of bounds write in Skia

Other sources

Google Skia contains an out-of-bounds write vulnerability that could allow a remote attacker to perform out of bounds memory access via a crafted HTML page. This vulnerability affects Google Chrome and ChromeOS, Android, Flutter, and possibly other products.

— CISA

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)

— MITRE

This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information. Google is aware that an exploit for CVE-2026-3909 exists in the wild.

— Microsoft

Credit

Google Threat Analysis Group

Affected Software

32 affected componentsFixes available
Google Chrome<146.0.7680.75
Microsoft Edge (Chromium-based)
Patch available
Microsoft Edge<146.0.3856.62
All of the following
Google Chrome<146.0.7680.80
Any of the following
Apple macOS
Linux Linux kernel
Microsoft Windows
Google Skia
Google Chrome<146.0.7680.80
146.0.7680.80
ubuntu/qtwebkit-opensource-src*
ubuntu/webkit2gtk*
ubuntu/qtwebkit-source*
ubuntu/webkitgtk*
ubuntu/webkit2gtk*
ubuntu/qtwebkit-opensource-src*
ubuntu/qtwebkit-source*
ubuntu/webkitgtk*
ubuntu/webkit2gtk*
ubuntu/qtwebkit-opensource-src*
ubuntu/wpewebkit*
ubuntu/qtwebkit-opensource-src*
ubuntu/webkit2gtk*
ubuntu/wpewebkit*
ubuntu/qtwebkit-opensource-src*
ubuntu/webkit2gtk*
ubuntu/webkit2gtk*
ubuntu/webkit2gtk*
alpine/qt6-qtwebengine<6.10.1-r10
6.10.1-r10
alpine/qt6-qtwebengine<6.10.2-r8
6.10.2-r8
debian/chromium
150.0.7871.100-1~deb12u1156.0.8078.79-1~deb12u1150.0.7871.181-1~deb13u1156.0.8078.79-1~deb13u1156.0.8078.79-1
debian/webkit2gtk<=2.50.6-1~deb12u2, <=2.50.6-1~deb12u1, <=2.52.6-1~deb13u1, <=2.52.6-1
2.54.0-1~deb13u32.54.2-2
debian/wpewebkit<=2.38.6-1, <=2.48.3-1
2.54.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 146.0.7680.80
  2. Upgrade

    Upgrade alpine/qt6-qtwebengine to a version that resolves this vulnerability.

    Fixed in 6.10.1-r10
  3. Upgrade

    Upgrade alpine/qt6-qtwebengine to a version that resolves this vulnerability.

    Fixed in 6.10.2-r8
  4. Upgrade

    Upgrade debian/chromium to a version that resolves this vulnerability.

    Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.79-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.79-1~deb13u1Fixed in 156.0.8078.79-1
  5. Upgrade

    Upgrade debian/webkit2gtk to a version that resolves this vulnerability.

    Fixed in 2.54.0-1~deb13u3Fixed in 2.54.2-2
  6. Upgrade

    Upgrade debian/wpewebkit to a version that resolves this vulnerability.

    Fixed in 2.54.2-1
  7. Upgrade

    Upgrade Google Chrome to a version that resolves this vulnerability.

    Fixed in 146.0.7680.75

Event History

Mar 10, 2026
CVE Published
12:00 AM
Data Sourced
12:00 AM
SeverityWeaknessAffected Software
Mar 12, 2026
CVE Published
via MITRE·09:30 PM
Data Sourced
via MITRE·09:30 PM
DescriptionWeakness
Data Sourced
via Red Hat·10:01 PM
DescriptionSeverityAffected Software
Mar 13, 2026
Data Sourced
via CISA·12:00 AM
RemedyDescriptionWeaknessAffected Software
News Published
via The Register·11:25 AM
Data Sourced
via OSV·07:55 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:55 PM
DescriptionSeverityWeaknessAffected Software
Mar 17, 2026
Data Sourced
via Microsoft·01:09 AM
DescriptionSeverityWeaknessAffected Software
Apr 1, 2026
News Published
via BleepingComputer·10:25 AM

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2026-3909?

The severity of CVE-2026-3909 is classified as High.

2

How do I fix CVE-2026-3909?

To fix CVE-2026-3909, update Google Chrome to version 146.0.7680.75 or later.

3

What causes CVE-2026-3909?

CVE-2026-3909 is caused by an out of bounds write in Skia within Google Chrome.

4

Can CVE-2026-3909 be exploited remotely?

Yes, CVE-2026-3909 can be exploited remotely through crafted HTML pages.

5

Which versions of Google Chrome are affected by CVE-2026-3909?

Google Chrome versions prior to 146.0.7680.75 are affected by CVE-2026-3909.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203