CVE-2026-3913: Critical Heap buffer overflow in WebML.
Chromium: CVE-2026-3913 Heap buffer overflow in WebML
Other sources
Heap buffer overflow in WebML in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
— 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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/chromiumto a version that resolves this vulnerability.Fixed in 150.0.7871.100-1~deb12u1Fixed in 156.0.8078.73-1~deb12u1Fixed in 150.0.7871.181-1~deb13u1Fixed in 156.0.8078.73-1~deb13u1Fixed in 156.0.8078.47-1Fixed in 156.0.8078.73-1 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 146.0.7680.71 - Upgrade
Upgrade
Microsoft Edge (Chromium-based)to a version that resolves this vulnerability.Fixed in 146.0.7680.71
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2026-3913?
CVE-2026-3913 has a critical severity rating due to the potential for remote exploitation via heap corruption.
How do I fix CVE-2026-3913?
To fix CVE-2026-3913, update Google Chrome to version 146.0.7680.71 or later.
What is the impact of CVE-2026-3913?
CVE-2026-3913 can allow remote attackers to potentially exploit heap corruption through a malicious HTML page.
Which versions of Google Chrome are affected by CVE-2026-3913?
CVE-2026-3913 affects Google Chrome versions prior to 146.0.7680.71.
Is there a workaround for CVE-2026-3913?
There are no known effective workarounds for CVE-2026-3913; updating Chrome is the recommended action.