CVE-2026-3543: Inappropriate implementation in V8
Chromium: CVE-2026-3543 Inappropriate implementation in V8
Other sources
Inappropriate implementation in V8 in Google Chrome prior to 145.0.7632.159 allowed a remote attacker to potentially 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
Credit
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
Chromiumto 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-3543?
CVE-2026-3543 has been classified as having a high severity due to its potential for allowing out of bounds memory access.
How do I fix CVE-2026-3543?
To fix CVE-2026-3543, ensure that you are using Google Chrome version 145.0.7632.159 or later.
What types of attacks can exploit CVE-2026-3543?
CVE-2026-3543 can potentially allow a remote attacker to exploit it via a crafted HTML page.
Which versions of Google Chrome are impacted by CVE-2026-3543?
CVE-2026-3543 affects all versions of Google Chrome prior to 145.0.7632.159.
Is there a workaround for CVE-2026-3543?
There are no known workarounds for CVE-2026-3543 other than upgrading to the patched version.