CVE-2018-17463 — Google Chromium V8 Remote Code Execution Vulnerability

CVE-2018-17463

A crafted HTML page exploits a V8 engine flaw for sandboxed code execution across Chrome, Edge, and other Chromium browsers

What is Chromium V8?

V8 is Google's open-source JavaScript and WebAssembly engine, developed for the Chrome browser and now embedded in every Chromium-based browser (Chrome, Microsoft Edge, Opera, Brave, and others) as well as in server-side runtimes like Node.js. As the component responsible for parsing and executing untrusted JavaScript from any website a user visits, V8 is one of the highest-value attack surfaces in modern computing — a flaw here can be triggered simply by getting a victim to load a web page.

Overview

CVE-2018-17463 is a vulnerability in the V8 JavaScript engine that allows a remote attacker to execute code inside the browser's renderer sandbox via a specially crafted HTML page. Because V8 is shared across all Chromium-based browsers, the vulnerability's impact extended beyond Google Chrome to Microsoft Edge (post-Chromium transition context notwithstanding for the 2018 timeframe), Opera, and other Chromium derivatives.

Technical Details

The exact memory-safety root cause was not broadly detailed in public NVD records at disclosure (the CWE field is not populated in NVD for this CVE), consistent with Google's typical practice of restricting technical details on browser vulnerabilities until a large majority of users have updated. What is documented is the impact: a crafted HTML/JavaScript page can trigger code execution confined to the browser's renderer sandbox (CVSS 8.8: network vector, low complexity, user interaction required to visit the malicious page). As with most V8 renderer bugs, this typically requires chaining with a separate sandbox-escape vulnerability to achieve code execution on the underlying OS outside the browser sandbox.

Discovery

The vulnerability was addressed through Google's standard Chrome security release process; specific external researcher credit for this particular CVE is not confidently documented in public sources reviewed here.

Exploitation Context

CISA's KEV entry confirms this vulnerability has been exploited in the wild. V8 renderer bugs are a recurring target for both cybercriminal exploit kits and more sophisticated attackers, often chained with sandbox-escape or kernel privilege-escalation bugs to achieve full system compromise from a single malicious web page visit.

Remediation

  1. Ensure Google Chrome, Microsoft Edge, Opera, and any other Chromium-based browser in use is updated to the latest version, which includes the V8 fix.
  2. Enable automatic browser updates organization-wide so renderer-engine fixes are applied promptly without manual intervention.
  3. Deploy browser isolation or sandboxing technology for high-risk user populations where feasible.
  4. Educate users on the risk of visiting untrusted links, since exploitation requires only loading a crafted web page.
  5. Monitor endpoint detection tooling for anomalous browser process behavior that could indicate renderer exploitation.

Key Details

PropertyValue
CVE ID CVE-2018-17463
Vendor / Product Google — Chromium V8
NVD Published2018-11-14
NVD Last Modified2025-10-24
CVSS 3.1 Score8.8
CVSS 3.1 VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
SeverityHIGH
CISA KEV Added2022-06-08
CISA KEV Deadline2022-06-22
Known Ransomware Use No

CVSS 3.1 Breakdown

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Required Action

CISA BOD 22-01 Deadline: 2022-06-22. Apply updates per vendor instructions.

Timeline

DateEvent
2018-09Google Chrome stable channel update released, fixing the V8 vulnerability
2018-11-14CVE published
2022-06-08Added to CISA Known Exploited Vulnerabilities catalog
2022-06-22CISA BOD 22-01 remediation deadline

References

ResourceType
NVD — CVE-2018-17463 Vulnerability Database
CISA KEV Catalog Entry US Government