dbcve.org
ChromeWeb browser · Google

CVE-2018-6118

HIGH · 8.8 CVSS v3.0 Published 2019-06-27
Fix available
A fix is available. Upgrade to 66.0.3359.139 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code 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

A double-eviction race condition in Google Chrome's Incognito mode cache created a use-after-free vulnerability. An attacker who had already compromised the renderer process could exploit this to achieve arbitrary code execution via a specially crafted HTML page.

MitigationUpgrade Google Chrome to version 66.0.3359.139 or later to patch the 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:< 66.0.3359.139

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.0/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. Verify Google Chrome is installed
    Check for Chrome executable (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or look for chrome package via package manager on Linux)
    Affected if Chrome browser is present on the system
  2. Determine installed Chrome version
    Navigate to Chrome menu > Help > About Google Chrome, or enter chrome://version in the address bar, or run 'google-chrome --version' on Linux command line
    Affected if Unable to determine version number (Chrome may be installed but version cannot be verified)
  3. Compare version against affected range
    Note the full version number displayed (e.g., 66.0.3359.117) and compare the first four numeric segments to 66.0.3359.139
    Affected if Installed version is less than 66.0.3359.139 (e.g., 65.x.x.x or 66.0.3359.138 or lower)
  4. Note Incognito usage context
    The vulnerability exists in Incognito mode cache behavior - while version check applies universally, active Incognito browsing sessions provide the specific attack surface
    Affected if Running vulnerable Chrome version AND using Incognito mode with untrusted web content

User is affected if Google Chrome version is below 66.0.3359.139, with Incognito mode being the specific context where the double-eviction race condition manifests.

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.

From vendor data
Upgrade available Upgrade to 66.0.3359.139 or later
Fixed in 66.0.3359.139
Interim mitigation

Upgrade Google Chrome to version 66.0.3359.139 or later to patch the vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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-6118 — 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-6118 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