CVE-2026-3542: High Inappropriate implementation in WebAssembly
Chromium: CVE-2026-3542 Inappropriate implementation in WebAssembly
Other sources
Inappropriate implementation in WebAssembly in Google Chrome prior to 145.0.7632.159 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.
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 145.0.7632.159 - Upgrade
Upgrade
alpine/chromiumto a version that resolves this vulnerability.Fixed in 144.0.7559.132-r4 - Upgrade
Upgrade
alpine/qt6-qtwebengineto a version that resolves this vulnerability.Fixed in 6.10.1-r9 - Upgrade
Upgrade
alpine/qt6-qtwebengineto a version that resolves this vulnerability.Fixed in 6.10.2-r6 - Upgrade
Upgrade
debian/chromiumto 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 - Upgrade
Upgrade
Google Chrometo a version that resolves this vulnerability.Fixed in 145.0.7632.159
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2026-3542?
CVE-2026-3542 has a high severity level due to the potential for remote attackers to exploit out of bounds memory access.
How do I fix CVE-2026-3542?
To fix CVE-2026-3542, update Google Chrome to version 145.0.7632.159 or later.
What types of systems are affected by CVE-2026-3542?
CVE-2026-3542 affects Google Chrome versions prior to 145.0.7632.159 on all platforms.
What can an attacker achieve by exploiting CVE-2026-3542?
An attacker exploiting CVE-2026-3542 can perform out of bounds memory access, potentially leading to arbitrary code execution.
Is there a workaround for CVE-2026-3542?
There is no specific workaround recommended for CVE-2026-3542; the best mitigation is to apply the security update.