dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jun 2022.
ChromeWeb browser · Google

CVE-2018-6065

HIGH · 8.8 CVSS v3.1 Published 2018-11-14
Fix available
A fix is available. Upgrade to 65.0.3325.146 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Integer overflow in V8 JavaScript engine's allocation size calculation allows a remote attacker to trigger heap corruption via a crafted HTML page. The overflow occurs when computing memory requirements for new JavaScript objects, potentially enabling heap-based buffer overflow exploitation.

MitigationUpdate Google Chrome to version 65.0.3325.146 or later to patch the V8 integer overflow vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 65.0.3325.146
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Debian LinuxOperating system
Affected:= 9.0
Mi6 BrowserApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version on Windows or Mac
    Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number is displayed on that page.
    Affected if The displayed version is less than 65.0.3325.146
  2. Check Google Chrome version via command line (Windows)
    Open Command Prompt and run: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome' /v Version
    Affected if The reported Version value is lower than 65.0.3325.146
  3. Check Chromium version on Linux systems
    Run 'chromium --version' or 'chromium-browser --version' in terminal
    Affected if The reported version is less than 65.0.3325.146
  4. Check Chrome version on Linux systems
    Run 'google-chrome --version' in terminal
    Affected if The reported version is less than 65.0.3325.146
  5. Check Mi6 Browser version on Android devices
    Open the Mi6 Browser app, go to Settings, then About to view the version number
    Affected if The Mi6 Browser is installed (all versions are affected according to the advisory)

If the installed Chrome or Chromium browser version is below 65.0.3325.146, or if the Mi6 Browser is present on the device, the environment is vulnerable to CVE-2018-6065.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 65.0.3325.146 or later
Fixed in 65.0.3325.146
Interim mitigation

Update Google Chrome to version 65.0.3325.146 or later to patch the V8 integer overflow vulnerability.

Recommended fix High confidence

Chrome 65.0.3325.146 or later

  1. Update Google Chrome to version 65.0.3325.146 or later
  2. On Linux systems, run: sudo yum update google-chrome-stable or sudo apt-get update && sudo apt-get install google-chrome-stable
  3. On Windows/Mac, Chrome typically auto-updates; verify version at chrome://settings/help
  4. For Enterprise Linux 6.0 and Debian 9.0 systems, apply the Chrome update via the system's package manager

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-6065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-6065 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data