CVE-2026-4444 — Stack-based Buffer Overflow in Google Chrome

CWE-121 — Stack-based Buffer OverflowCWE-120 — Classic Buffer Overflow9 documents9 sources
Severity
8.8HIGHNVD
EPSS
0.1%
top 79.13%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
2
Google ChromeChromium
Timeline
PublishedMar 20

Description

Stack buffer overflow in WebRTC in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit stack corruption via a crafted HTML page. (Chromium security severity: High)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitability: 2.8 | Impact: 5.9

Affected Packages3 packages

▶CVEListV5google/chrome146.0.7680.153 — 146.0.7680.153
▶NVDgoogle/chrome< 146.0.7680.153
▶Debianchromium/chromium< 146.0.7680.153-1~deb12u1+2

🔴Vulnerability Details

3
GHSA
GHSA-9f48-pfwp-h463: Stack buffer overflow in WebRTC in Google Chrome prior to 146↗2026-03-20
▶
OSV
CVE-2026-4444: Stack buffer overflow in WebRTC in Google Chrome prior to 146↗2026-03-20
▶
CVEList
CVE-2026-4444: Stack buffer overflow in WebRTC in Google Chrome prior to 146↗2026-03-20
▶

📋Vendor Advisories

4
Red Hat
chromium-browser: Stack buffer overflow in WebRTC↗2026-03-18
▶
Chrome
Stable Channel Update for Desktop: CVE-2026-4442↗2026-03-18
▶
Microsoft
Chromium: CVE-2026-4444 Stack buffer overflow in WebRTC↗2026-03-10
▶
Debian
CVE-2026-4444: chromium - Stack buffer overflow in WebRTC in Google Chrome prior to 146.0.7680.153 allowed...↗2026
▶

🕵️Threat Intelligence

1
Wiz
CVE-2026-4444 Impact, Exploitability, and Mitigation Steps | Wiz↗
▶
CVE-2026-4444 — Stack-based Buffer Overflow in Google | cvebase