Skip to content
skopnix

CVE-2018-17463 · Published 14 Nov 2018

Google Chromium V8

On CISA's KEV list 1302 days after disclosure; 4 public exploits.

Google Chromium V8 Engine contains an unspecified vulnerability that allows a remote attacker to execute code inside a sandbox via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

CISA required action (federal due date 22 Jun 2022): Apply updates per vendor instructions.

Signals

KEV, exploited in the wild
yes, added 8 Jun 2022, due 22 Jun 2022
EPSS, 30-day forecast
85%, 100th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

KEV is an observation, EPSS a forecast; KEV outranks it. No score published by NVD.

Timeline 14 Nov 2018 to today

821 days from the first proof of concept to the KEV listing
2021202420252026Disclosed 14 Nov 2018Metasploit 14 Feb 2020First PoC 9 Mar 2020KEV 8 Jun 2022today
  1. Disclosed
  2. Metasploit+457 d
  3. First PoC+24 d
  4. KEV+821 d

821 days from the first proof of concept to the KEV listing

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 0 dispatches

No dispatch on our wire has named this CVE yet.

Public exploit code 4 known · links only

GitHub PoCs 2Metasploit 1Exploit-DB 1

GitHub PoCs, by trust then stars2

  1. first seen by skopnix 18 Oct 2026

  2. first seen by skopnix 18 Oct 2026

Fake proof-of-concept repositories have been used to deliver malware to the researchers who run them. The trust verdict is our engine's heuristic over the repository (account age, what it ships, how its stars arrived); it is a reason to read the code first, not a finding about its author.

Metasploit1

  1. This modules exploits a type confusion in Google Chromes JIT compiler. The Object.create operation can be used to cause a type confusion between a PropertyArray and a NameDictionary. The payload is executed within the rwx region of the sandboxed renderer process. This module can target the renderer process (target 0), but Google Chrome must be launched with the --no-sandbox flag for the payload to execute successfully.

    ruby · first seen by skopnix 18 Oct 2026

Exploit-DB1

  1. created 9 Mar 2020

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check