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-2019-5825

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-25
Fix available
A fix is available. Upgrade to 73.0.3683.86 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Patch available

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
Out of bounds write in JavaScript in Google Chrome prior to 73.0.3683.86 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

An out-of-bounds write vulnerability in the JavaScript engine of Google Chrome versions prior to 73.0.3683.86 allows a remote attacker to corrupt heap memory via a specially crafted HTML page.

MitigationUpdate Google Chrome to version 73.0.3683.86 or later to remediate 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:< 73.0.3683.86

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
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 checks

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

  1. Check installed Chrome version via browser UI
    Open a new tab and navigate to chrome://version. Locate the 'Version' field in the displayed information.
    Affected if The version number displayed is lower than 73.0.3683.86 (for example, 73.0.3683.75 or any earlier version).
  2. Check 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 returned version value is less than 73.0.3683.86.
  3. Check Chrome version via command line (macOS)
    Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
    Affected if The displayed version is lower than 73.0.3683.86.
  4. Check Chrome version via command line (Linux)
    Open Terminal and run: google-chrome --version or chrome --version
    Affected if The version output is less than 73.0.3683.86.

A system is affected if Google Chrome is installed and its version is below 73.0.3683.86, as the out-of-bounds write vulnerability exists in all prior versions.

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 73.0.3683.86 or later
Fixed in 73.0.3683.86
Vendor patch crbug.com →
Interim mitigation

Update Google Chrome to version 73.0.3683.86 or later to remediate the vulnerability.

Recommended fix High confidence

Chrome 73.0.3683.86 or later

  1. Upgrade Google Chrome to version 73.0.3683.86 or later
  2. To upgrade: Click the menu icon (three dots) > Help > About Google Chrome
  3. The browser will automatically check for and install the latest version
  4. Restart Chrome after the update completes
Caveat Major version upgrades may introduce user interface or feature changes

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5825 — 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-2019-5825 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