CVE-2026-4457: Type Confusion in V8
Chromium: CVE-2026-4457 Type Confusion in V8
Other sources
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
Type Confusion in V8 in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
— NVD
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-4444
- 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-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-4457?
CVE-2026-4457 has a high severity rating due to the potential for remote exploitation of heap corruption in Google Chrome.
How do I fix CVE-2026-4457?
To fix CVE-2026-4457, update Google Chrome to version 146.0.7680.153 or later.
What versions of Google Chrome are affected by CVE-2026-4457?
CVE-2026-4457 affects all versions of Google Chrome prior to 146.0.7680.153.
Can CVE-2026-4457 be exploited through a crafted HTML page?
Yes, CVE-2026-4457 can be exploited by a remote attacker through a specially crafted HTML page.
What impact does CVE-2026-4457 have on users?
CVE-2026-4457 can lead to heap corruption, which may allow attackers to execute arbitrary code on the affected system.