CVE-2018-6065 · Published 14 Nov 2018
Google Chromium V8
On CISA's KEV list 1302 days after disclosure; 2 public exploits; 1 attacker cited in reports.
Google Chromium V8 Engine contains an integer overflow vulnerability that allows a remote attacker to potentially exploit heap corruption 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
- 60%, 99th 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 4 May 2018 to today
- First PoC
- Disclosed+194 d
- KEV+1302 d
1,302 days from disclosure to the KEV listing
Who exploits it 1 citation
- POISON CARP
“Other exploits include what appears to be lightly modified versions of Chrome exploit code published on the personal GitHub pages of a member of Tencent’s Xuanwu Lab ( CVE-2016-1646 ), a member of Qihoo 360’s Vulcan Team ( CVE-2018-17480 ), and by a Google Project Zero member on the Chrome Bug Tracker ( CVE-2018-6065 ).”
cited as exploiting · named nearby · citizenlab.ca ↗ · 17 Oct 2026
Each actor is cited by the quoted source, linked under the quote. A citation is that source's claim, not our confirmation.
Linked 1 in our graph
Exploited by
- actorPOISON CARP
Links our graph holds for this CVE, strongest first. The same data is in the graph API.
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 2 known · links only
GitHub PoCs 1Metasploit 0Exploit-DB 1
GitHub PoCs, by trust then stars1
- b1tg/CVE-2018-6065-exploitNot checked
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.
Exploit-DB1
created 4 May 2018
References
Watch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.