CVE-2026-4462: Medium Out of bounds read in Blink
Chromium: CVE-2026-4462 Out of bounds read in Blink
Other sources
Out of bounds read in Blink in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to perform an out of bounds memory read 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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/qt6-qtwebengineto a version that resolves this vulnerability.Fixed in 6.10.1-r12 - Upgrade
Upgrade
alpine/qt6-qtwebengineto a version that resolves this vulnerability.Fixed in 6.10.2-r11 - 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 146.0.7680.153
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2026-4462?
CVE-2026-4462 is classified as having a high severity due to the potential for remote exploitation via out of bounds memory reads.
How do I fix CVE-2026-4462?
To fix CVE-2026-4462, update Google Chrome to version 146.0.7680.153 or later.
What types of attacks are possible with CVE-2026-4462?
CVE-2026-4462 allows remote attackers to perform out of bounds memory reads through a crafted HTML page.
What versions of Google Chrome are affected by CVE-2026-4462?
CVE-2026-4462 affects all versions of Google Chrome prior to 146.0.7680.153.
Is there a workaround for CVE-2026-4462?
There is no known workaround for CVE-2026-4462; the best solution is to update to the latest version of Chrome.