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.
CVE-2018-6065
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-06-08), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS
- 99.0%
- KEV
- ⚠ Exploited
Published
November 14, 2018
Last Modified
October 24, 2025
Advisory Details (7)
Auto-updated Jun 2, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.htmlAffected: Red Hat Enterprise Linux 6 Supplementary.
https://access.redhat.com/errata/RHSA-2018:0484Google Chrome V8 - Object Allocation Size Integer Overflow - Multiple remote Exploit
https://www.exploit-db.com/exploits/44584/[SECURITY] [DSA 4182-1] chromium-browser security update
https://www.debian.org/security/2018/dsa-4182Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | chromium-browser-0:65.0.3325.146-2.el6_9 | 2018-03-12 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 85× in last 7d / 395× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 722 total refreshes for this CVE.
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:37 UTCEG score recompute
- 2026-07-22 21:45 UTCEG score recompute
- 2026-07-22 21:45 UTCVendor advisory
- 2026-07-22 21:45 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 17:33 UTCEG score recompute
- 2026-07-22 17:33 UTCVendor advisory
- 2026-07-22 17:32 UTCGHSA enrichment
- 2026-07-22 14:05 UTCEPSS rescore
- 2026-07-22 13:32 UTCVendor advisory
- 2026-07-22 13:32 UTCGHSA enrichment
- 2026-07-22 09:33 UTCVendor advisory
- 2026-07-22 09:33 UTCGHSA enrichment
- 2026-07-22 05:34 UTCVendor advisory
- 2026-07-22 05:34 UTCGHSA enrichment
- 2026-07-22 01:35 UTCVendor advisory
- 2026-07-22 01:35 UTCGHSA enrichment
- 2026-07-21 21:36 UTCVendor advisory
- 2026-07-21 21:35 UTCGHSA enrichment
- 2026-07-21 17:34 UTCEG score recompute
- 2026-07-21 17:34 UTCVendor advisory
- 2026-07-21 17:34 UTCGHSA enrichment
- 2026-07-21 15:22 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 13:35 UTCVendor advisory
- 2026-07-21 13:35 UTCGHSA enrichment
- 2026-07-21 09:36 UTCVendor advisory
- 2026-07-21 09:35 UTCGHSA enrichment
- 2026-07-21 05:35 UTCVendor advisory
- 2026-07-21 05:35 UTCGHSA enrichment
- 2026-07-21 01:35 UTCVendor advisory
- 2026-07-21 01:35 UTCGHSA enrichment
- 2026-07-20 21:36 UTCVendor advisory
- 2026-07-20 21:36 UTCGHSA enrichment
- 2026-07-20 17:35 UTCEG score recompute
- 2026-07-20 17:35 UTCVendor advisory
- 2026-07-20 17:35 UTCGHSA enrichment
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 13:36 UTCVendor advisory
- 2026-07-20 13:36 UTCGHSA enrichment
- 2026-07-20 09:37 UTCVendor advisory
- 2026-07-20 09:37 UTCGHSA enrichment
- 2026-07-20 05:37 UTCVendor advisory
- 2026-07-20 05:37 UTCGHSA enrichment
- 2026-07-20 01:38 UTCVendor advisory
- 2026-07-20 01:38 UTCGHSA enrichment
- 2026-07-19 21:39 UTCVendor advisory
- 2026-07-19 21:39 UTCGHSA enrichment
- 2026-07-19 17:40 UTCEG score recompute
- 2026-07-19 17:40 UTCVendor advisory
- 2026-07-19 17:40 UTCGHSA enrichment
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 13:41 UTCVendor advisory
- 2026-07-19 13:41 UTCGHSA enrichment
- 2026-07-19 09:42 UTCVendor advisory
- 2026-07-19 09:42 UTCGHSA enrichment
- 2026-07-19 05:43 UTCEG score recompute
- 2026-07-19 05:43 UTCVendor advisory
- 2026-07-19 05:43 UTCGHSA enrichment
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 01:44 UTCVendor advisory
- 2026-07-19 01:43 UTCGHSA enrichment
- 2026-07-18 21:44 UTCVendor advisory
- 2026-07-18 21:44 UTCGHSA enrichment
- 2026-07-18 17:45 UTCVendor advisory
- 2026-07-18 17:45 UTCGHSA enrichment
- 2026-07-18 13:46 UTCVendor advisory
- 2026-07-18 13:46 UTCGHSA enrichment
- 2026-07-18 09:47 UTCVendor advisory
- 2026-07-18 09:47 UTCGHSA enrichment
- 2026-07-18 05:48 UTCVendor advisory
- 2026-07-18 05:48 UTCGHSA enrichment
- 2026-07-18 01:49 UTCVendor advisory
- 2026-07-18 01:49 UTCGHSA enrichment
- 2026-07-17 21:50 UTCVendor advisory
- 2026-07-17 21:50 UTCGHSA enrichment
- 2026-07-17 17:51 UTCVendor advisory
- 2026-07-17 17:51 UTCGHSA enrichment
- 2026-07-17 13:51 UTCVendor advisory
- 2026-07-17 13:51 UTCGHSA enrichment
- 2026-07-17 09:52 UTCEG score recompute
- 2026-07-17 09:52 UTCVendor advisory
- 2026-07-17 09:52 UTCGHSA enrichment
- 2026-07-17 05:53 UTCVendor advisory
- 2026-07-17 05:52 UTCGHSA enrichment
- 2026-07-17 01:53 UTCVendor advisory
- 2026-07-17 01:52 UTCGHSA enrichment
- 2026-07-16 21:53 UTCVendor advisory
- 2026-07-16 21:53 UTCGHSA enrichment
- 2026-07-16 17:54 UTCVendor advisory
- 2026-07-16 17:54 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 13:55 UTCVendor advisory
Publicly available exploits
(2 references)Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoCb1tg/CVE-2018-6065-exploitFirst seen Apr 24, 2021
- Exploit-DBEDB-44584✓ verifiedFirst seen May 4, 2018
Google Chrome V8 - Object Allocation Size Integer Overflow
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-190 · CWE-787
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(6)
What is CVE-2018-6065?
When was CVE-2018-6065 disclosed?
Is CVE-2018-6065 actively exploited?
What is the CVSS score of CVE-2018-6065?
Which products are affected by CVE-2018-6065?
How do I remediate CVE-2018-6065?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2018-6065
Is Your Infrastructure Affected by CVE-2018-6065?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.