CVE-2026-16418: Stack buffer overflow in V8
Chromium: CVE-2026-16418 Stack buffer overflow in V8
Other sources
Stack buffer overflow in V8 in Google Chrome prior to 150.0.7871.182 allowed a remote attacker to execute arbitrary code inside a sandbox 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 150.0.7871.181 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 150.0.4078.96 - Upgrade
Upgrade
Google Chrome / Chromium-based (including Microsoft Edge)to a version that resolves this vulnerability.Fixed in 150.0.7871.182
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2026-16418?
The severity of CVE-2026-16418 is classified as High.
How do I fix CVE-2026-16418?
To fix CVE-2026-16418, update Google Chrome to version 150.0.7871.182 or later.
What type of vulnerability is CVE-2026-16418?
CVE-2026-16418 is a stack buffer overflow vulnerability in the V8 engine of Google Chrome.
Can CVE-2026-16418 allow remote code execution?
Yes, CVE-2026-16418 allows a remote attacker to execute arbitrary code inside a sandbox.
What software is affected by CVE-2026-16418?
CVE-2026-16418 affects Google Chrome and the Google V8 JavaScript engine.