ChromeWeb browser · Google
CVE-2019-5846
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 · uneditedOut of bounds access in SwiftShader in Google Chrome prior to 73.0.3683.75 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 confidenceAn out-of-bounds memory access vulnerability in SwiftShader (Google's software graphics renderer) in Google Chrome versions prior to 73.0.3683.75 allows a remote attacker to potentially exploit heap corruption through a specially 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
< 73.0.3683.75= 15.0= 15.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help in the browser, or run 'google-chrome --version' from command line on Linux, or select 'About Google Chrome' from the Chrome menu on MacAffected if The displayed version is earlier than 73.0.3683.75 (e.g., 72.x or earlier)
-
Verify SwiftShader is available or enabledOpen chrome://gpu and look for 'SwiftShader' under the 'Graphics Feature Status' section, or access chrome://flags and search for 'SwiftShader' related settingsAffected if SwiftShader is listed as available or the 'Override software rendering' flag is enabled
-
Confirm software rendering is in useOpen chrome://gpu and check the 'Driver' field for SwiftShader, or observe if the browser is using software rendering (no hardware GPU acceleration)Affected if The browser is using SwiftShader for rendering (typically indicated by software rendering mode being active)
-
On affected SUSE systems, verify package versionOn OpenSUSE Leap 15.1 or Backports Sle 15.0, run 'rpm -qa | grep google-chrome' to check the installed package versionAffected if The installed Chrome package version is earlier than the version that includes the 73.0.3683.75 security patch
You are affected if Google Chrome version is earlier than 73.0.3683.75 AND SwiftShader software rendering is in active use on your system.
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 data73.0.3683.75
Update Google Chrome to version 73.0.3683.75 or later to patch the vulnerability in SwiftShader.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5846 — 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-2019-5846 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