CVE-2026-3909: Google Skia Out-of-Bounds Write
Google Skia · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-13.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 2.3%
- higher than 83.9% of all CVEs
- Added to CISA KEV
- 2026-03-13
- US federal due date 2026-03-27
- Ubuntu priority
- high
CVE-2026-3909 explained
CVE-2026-3909 is an out-of-bounds write in the Skia graphics library used by Google Chrome before 146.0.7680.75. A crafted HTML page can trigger out-of-bounds memory access. CISA lists it as known exploited, and Ubuntu rates its priority as high, so browser and web engine packages that ship the affected code should be patched quickly.
Impact
A remote attacker can host or deliver a crafted HTML page. If a user opens it in an affected browser or web engine, the attacker can cause out-of-bounds memory access. No privileges are needed, but user interaction is required. Successful exploitation can have high impact on confidentiality, integrity and availability. In practice this can mean data exposure, memory corruption or a crash of the affected application.
Who is affected
Debian chromium is fixed in Debian 12 (bookworm) (146.0.7680.80-1~deb12u1), Debian 13 (trixie) (146.0.7680.80-1~deb13u1) and testing Debian 14 (forky) (146.0.7680.80-1). webkit2gtk is fixed in trixie (2.54.0-1~deb13u1). wpewebkit is fixed in forky (2.54.0-1). Debian no longer supports webkit2gtk in bookworm and will not fix it there. No fixed version is published for wpewebkit in bookworm and trixie, or for webkit2gtk in forky. On Ubuntu 16.04 LTS through Ubuntu 26.10, no fixed version is published for webkit2gtk, webkitgtk, wpewebkit, qtwebkit-opensource-src or qtwebkit-source.
Written with AI from the data on this page and checked against it automatically.
Official description
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)
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
- This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. Please check with specific vendors for information on patching status. For more information, please see: chromereleases.googleblog.com/2026/03/stable-channel-upda…
- nvd.nist.gov/vuln/detail/CVE-2026-3909
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 146.0.7680.75
- 146.0.7680.75
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 26.10·webkit2gtk
Status: no fixed version published · Ubuntu tracker
Ubuntu 26.04 LTS·webkit2gtk
Status: no fixed version published · Ubuntu tracker
Ubuntu 24.04 LTS·qtwebkit-opensource-src
Status: no fixed version published · Ubuntu tracker
Ubuntu 24.04 LTS·webkit2gtk
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·qtwebkit-opensource-src
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·webkit2gtk
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·wpewebkit
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·qtwebkit-opensource-src
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·webkit2gtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·wpewebkit
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·qtwebkit-opensource-src
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·qtwebkit-source
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·webkit2gtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·webkitgtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·qtwebkit-opensource-src
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·qtwebkit-source
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·webkit2gtk
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·webkitgtk
ESM ended
Status: no fixed version published · Ubuntu tracker
Debian 14 (forky)·chromium
testing distribution
Fixed: 146.0.7680.80-1
Debian 14 (forky)·webkit2gtk
testing distribution
Status: no fixed version published · Debian tracker
Debian 14 (forky)·wpewebkit
testing distribution
Fixed: 2.54.0-1
Debian 13 (trixie)·chromium
Fixed: 146.0.7680.80-1~deb13u1
Debian 13 (trixie)·webkit2gtk
Fixed: 2.54.0-1~deb13u1
Debian 13 (trixie)·wpewebkit
Status: no fixed version published · Debian tracker
Debian 12 (bookworm)·chromium
Fixed: 146.0.7680.80-1~deb12u1
Debian 12 (bookworm)·webkit2gtk
Status: Debian: package not supported, no fix
Debian 12 (bookworm)·wpewebkit
Status: no fixed version published · Debian tracker
What to do
- On Debian, update
chromiumto the fixed version for your release. - On Debian 13 (trixie), update
webkit2gtkto2.54.0-1~deb13u1. - After updating, restart all browser and web engine processes so they stop running the old code.
- Upgrade Ubuntu 16.04 LTS systems to a supported release.
- For Ubuntu 18.04 LTS and 20.04 LTS, use Ubuntu Pro (ESM) to receive future fixes, or upgrade to a supported release.
- Monitor the Ubuntu and Debian advisories for fixed packages that are still pending.
Until fixed packages are published, avoid opening untrusted web content with applications built on the unfixed web engine packages. Where possible, use an updated browser such as the patched chromium packages. Remove the unfixed packages if you do not need them. On Debian 12, webkit2gtk will receive no fix, so plan to replace or remove it, or move to Debian 13.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above (this CVE affects 6 source packages).
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
No fixed version yet on 6 releases
Ubuntu 26.10, Ubuntu 26.04 LTS, Ubuntu 24.04 LTS, Ubuntu 22.04 LTS, Ubuntu 20.04 LTS, Ubuntu 18.04 LTS: no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2026/03/stable-channel-upda…
- If the server does not need the package, remove it, or replace it with a maintained alternative.
- Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.
This page updates automatically when Ubuntu or Debian publish a fix.
Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out of bounds write
Questions about CVE-2026-3909
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-3909 to its Known Exploited Vulnerabilities catalog on 2026-03-13, with a US federal due date of 2026-03-27. Whether it has been used in ransomware is unknown.
- Does a fix take effect immediately after updating?
- No. Running browsers and applications that use the affected web engine keep the old code in memory. Restart them after the update so the fix takes effect.
- Can an attacker exploit this without user action?
- No. User interaction is required. A user must open a crafted HTML page in an affected application. No privileges are needed, and the attack works over the network.
Written with AI from the data on this page and checked against it automatically.
References
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.