ChromeWeb browser · Google
CVE-2018-6076
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 · uneditedInsufficient encoding of URL fragment identifiers in Blink in Google Chrome prior to 65.0.3325.146 allowed a remote attacker to perform a DOM based XSS attack 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 confidenceThis is a DOM-based XSS vulnerability in Google Chrome's Blink rendering engine. The issue stems from insufficient encoding of URL fragment identifiers (the portion after # in a URL), allowing a remote attacker to inject malicious scripts through a crafted HTML page.
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
< 65.0.3325.146
Linux DesktopOperating system
= 6.0
Linux ServerOperating system
= 6.0
Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.0CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check if Chrome or Chromium is installedOn Windows: Check for chrome.exe in Program Files or Program Files (x86). On Linux: Run 'which google-chrome chromium chromium-browser' or check /usr/bin/. On macOS: Check /Applications for Google Chrome.appAffected if Chrome or Chromium browser is present on the system
-
Determine the installed Chrome versionOn Windows: Right-click chrome.exe > Properties > Details > File Version, or navigate to chrome://settings/help. On Linux: Run 'google-chrome --version' or 'chromium --version'. On macOS: Right-click Google Chrome.app > Get Info > VersionAffected if Version is lower than 65.0.3325.146 (e.g., 65.0.3325.145 or earlier)
-
Check for bundled Chromium in Red Hat systemsRun 'rpm -qa | grep -i chromium' or 'rpm -qa | grep -i chrome' to list installed Chrome/Chromium packages and their versionsAffected if Package version is present and lower than 65.0.3325.146
-
Check for bundled Chromium in Debian systemsRun 'dpkg -l | grep -i chromium' or 'dpkg -l | grep -i chrome' to list installed Chrome/Chromium packages and their versionsAffected if Package version is present and lower than 65.0.3325.146
A system is affected if Google Chrome or Chromium browser is installed with a version number less than 65.0.3325.146.
Generated from the published advisory. Verify against your own configuration.
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 data65.0.3325.146
Update Google Chrome to version 65.0.3325.146 or later to remediate this vulnerability. Organizations should ensure all Chrome installations across their environment are patched.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,320.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-6076 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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