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 PROB
- 60%
- EPSS %ILE
- 99%
- 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.
Affected Packages
(1 across 1 ecosystem)
Debian:9(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium-browser | 59.0.3071.104-1 ... 66.0.3359.26-2 (30 versions) | 66.0.3359.117-1~deb9u1 | — |
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 99× in last 7d / 417× 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 1,515 total refreshes for this CVE.
- 2026-09-20 17:15 UTCVendor advisory
- 2026-09-20 17:15 UTCGHSA enrichment
- 2026-09-20 13:16 UTCVendor advisory
- 2026-09-20 13:16 UTCGHSA enrichment
- 2026-09-20 09:17 UTCVendor advisory
- 2026-09-20 09:17 UTCGHSA enrichment
- 2026-09-20 05:16 UTCVendor advisory
- 2026-09-20 05:16 UTCGHSA enrichment
- 2026-09-20 01:17 UTCVendor advisory
- 2026-09-20 01:17 UTCGHSA enrichment
- 2026-09-19 21:18 UTCVendor advisory
- 2026-09-19 21:18 UTCGHSA enrichment
- 2026-09-19 17:19 UTCEG score recompute
- 2026-09-19 17:19 UTCVendor advisory
- 2026-09-19 17:19 UTCGHSA enrichment
- 2026-09-19 15:36 UTCEPSS rescore
- 2026-09-19 13:20 UTCVendor advisory
- 2026-09-19 13:20 UTCGHSA enrichment
- 2026-09-19 09:21 UTCVendor advisory
- 2026-09-19 09:20 UTCGHSA enrichment
- 2026-09-19 05:18 UTCVendor advisory
- 2026-09-19 05:18 UTCGHSA enrichment
- 2026-09-19 01:19 UTCVendor advisory
- 2026-09-19 01:19 UTCGHSA enrichment
- 2026-09-18 21:20 UTCEG score recompute
Show 75 moreShow fewer
- 2026-09-18 21:20 UTCVendor advisory
- 2026-09-18 21:20 UTCGHSA enrichment
- 2026-09-18 19:22 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 17:22 UTCVendor advisory
- 2026-09-18 17:22 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 13:23 UTCVendor advisory
- 2026-09-18 13:23 UTCGHSA enrichment
- 2026-09-18 09:24 UTCVendor advisory
- 2026-09-18 09:24 UTCGHSA enrichment
- 2026-09-18 05:25 UTCVendor advisory
- 2026-09-18 05:25 UTCGHSA enrichment
- 2026-09-18 01:26 UTCVendor advisory
- 2026-09-18 01:26 UTCGHSA enrichment
- 2026-09-17 21:27 UTCEG score recompute
- 2026-09-17 21:27 UTCVendor advisory
- 2026-09-17 21:27 UTCGHSA enrichment
- 2026-09-17 19:22 UTCEPSS rescore
- 2026-09-17 17:28 UTCVendor advisory
- 2026-09-17 17:27 UTCGHSA enrichment
- 2026-09-17 12:52 UTCVendor advisory
- 2026-09-17 12:52 UTCGHSA enrichment
- 2026-09-17 08:51 UTCVendor advisory
- 2026-09-17 08:51 UTCGHSA enrichment
- 2026-09-17 04:52 UTCVendor advisory
- 2026-09-17 04:52 UTCGHSA enrichment
- 2026-09-17 00:53 UTCVendor advisory
- 2026-09-17 00:53 UTCGHSA enrichment
- 2026-09-16 20:54 UTCVendor advisory
- 2026-09-16 20:54 UTCGHSA enrichment
- 2026-09-16 16:41 UTCEG score recompute
- 2026-09-16 16:41 UTCVendor advisory
- 2026-09-16 16:41 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 12:37 UTCVendor advisory
- 2026-09-16 12:37 UTCGHSA enrichment
- 2026-09-16 08:39 UTCEG score recompute
- 2026-09-16 08:39 UTCVendor advisory
- 2026-09-16 08:38 UTCGHSA enrichment
- 2026-09-16 04:36 UTCVendor advisory
- 2026-09-16 04:36 UTCGHSA enrichment
- 2026-09-16 00:37 UTCVendor advisory
- 2026-09-16 00:37 UTCGHSA enrichment
- 2026-09-15 20:37 UTCVendor advisory
- 2026-09-15 20:37 UTCGHSA enrichment
- 2026-09-15 16:29 UTCVendor advisory
- 2026-09-15 16:29 UTCGHSA enrichment
- 2026-09-15 12:30 UTCVendor advisory
- 2026-09-15 12:30 UTCGHSA enrichment
- 2026-09-15 08:31 UTCVendor advisory
- 2026-09-15 08:31 UTCGHSA enrichment
- 2026-09-15 04:32 UTCEG score recompute
- 2026-09-15 04:32 UTCVendor advisory
- 2026-09-15 04:32 UTCGHSA enrichment
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-15 03:05 UTCEPSS rescore
- 2026-09-15 00:33 UTCVendor advisory
- 2026-09-15 00:33 UTCGHSA enrichment
- 2026-09-14 20:34 UTCVendor advisory
- 2026-09-14 20:34 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 16:35 UTCVendor advisory
- 2026-09-14 16:35 UTCGHSA enrichment
- 2026-09-14 12:36 UTCVendor advisory
- 2026-09-14 12:36 UTCGHSA enrichment
- 2026-09-14 08:37 UTCVendor advisory
- 2026-09-14 08:37 UTCGHSA enrichment
- 2026-09-14 04:38 UTCVendor advisory
- 2026-09-14 04:38 UTCGHSA enrichment
- 2026-09-14 00:40 UTCVendor advisory
- 2026-09-14 00:40 UTCGHSA enrichment
- 2026-09-13 20:40 UTCVendor advisory
- 2026-09-13 20:40 UTCGHSA enrichment
- 2026-09-13 16:41 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:RHSA-2018:0484
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
See which npm, PyPI, Go, and Maven packages are affected by 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.