PoC Monitor
← All CVEs
CVE-2018-6065published 14 Nov 2018 15:00 UTCData: JSON · API

Google Chrome

Google Chromium V8 Integer Overflow Vulnerability

Integer overflow in computing the required allocation size when instantiating a new javascript object in V8 in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

First public PoC 195 days beforebefore publication · 4 May 2018 · Exploit-DB
Public PoCs21 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS8.8high · scored by CISA ADP · CWE-190
CISA KEV 8 Jun 20223.6 years after publication

Timeline

Days relative to CVE publication
-180t=0+180+360+540+720+900+1080+1260First public PoC4 May 2018 · t−195dCVE published14 Nov 2018 · t = 0Added to CISA KEV8 Jun 2022 · t+3.6y

First public PoC 195 days before publication; added to CISA KEV 3.6 years after publication. First PoC: Google Chrome V8 - Object Allocation Size Integer Overflow (Exploit-DB, 4 May 2018).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
b1tg/CVE-2018-6065-exploit 24 Apr 2021 +2.4 y 2 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
CVE record (tagged exploit)44584unknown14 Nov 2026
Exploit-DBGoogle Chrome V8 - Object Allocation Size Integer Overflow4 May 201814 Nov 2026