CVE-2026-4444: Stack buffer overflow in WebRTC
Chromium: CVE-2026-4444 Stack buffer overflow in WebRTC
Other sources
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)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-4439
- CVE-2026-4440
- CVE-2026-4441
- CVE-2026-4442
- CVE-2026-4443
- CVE-2026-4445
- CVE-2026-4446
- CVE-2026-4447
- CVE-2026-4448
- CVE-2026-4449
- CVE-2026-4450
- CVE-2026-4451
- CVE-2026-4452
- CVE-2026-4453
- CVE-2026-4454
- CVE-2026-4455
- CVE-2026-4456
- CVE-2026-4457
- CVE-2026-4458
- CVE-2026-4459
- CVE-2026-4460
- CVE-2026-4461
- CVE-2026-4462
- CVE-2026-4463
- CVE-2026-4464
Frequently Asked Questions
What is the severity of CVE-2026-4444?
CVE-2026-4444 has a security severity rating of High.
How do I fix CVE-2026-4444?
To fix CVE-2026-4444, update Google Chrome to version 146.0.7680.153 or later.
What does CVE-2026-4444 affect?
CVE-2026-4444 affects Google Chrome versions prior to 146.0.7680.153.
What type of vulnerability is CVE-2026-4444?
CVE-2026-4444 is a stack buffer overflow vulnerability.
Can CVE-2026-4444 be exploited remotely?
Yes, CVE-2026-4444 can potentially be exploited by a remote attacker via a crafted HTML page.