dbcve.org
ChromeWeb browser · Google

CVE-2019-5868

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-25
Fix available
A fix is available. Upgrade to 76.0.3809.100 or later.
See remediation →
58/100
Remediation priority · Elevated
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
Use after free in PDFium in Google Chrome prior to 76.0.3809.100 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file.

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 use-after-free vulnerability exists in PDFium (Google Chrome's PDF rendering engine) prior to version 76.0.3809.100. The flaw allows a remote attacker to potentially exploit heap corruption by tricking a user into opening a specially crafted malicious PDF file.

MitigationUpdate Google Chrome to version 76.0.3809.100 or later. Organizations should ensure patch management processes include browser updates and enforce automatic updates where possible.

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:< 76.0.3809.100

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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. Determine installed Google Chrome version
    Open chrome://settings/help in the Chrome browser, or run 'google-chrome --version' from command line
    Affected if The displayed version is less than 76.0.3809.100
  2. Confirm Chrome channel and update status
    Navigate to chrome://settings/help and check if Chrome indicates it is up to date, or check if automatic updates are enabled under chrome://settings/advanced
    Affected if Chrome reports an available update or shows a version below 76.0.3809.100 as current
  3. Verify PDFium component presence
    PDFium is integrated into Chrome and handles PDF rendering. Confirm PDF functionality works by opening any PDF file in the browser
    Affected if PDFs render successfully (indicating PDFium is active) and Chrome version is below 76.0.3809.100

A user is affected if their Google Chrome installation version is below 76.0.3809.100 and they can open PDF files in the browser.

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 76.0.3809.100 or later
Fixed in 76.0.3809.100
Interim mitigation

Update Google Chrome to version 76.0.3809.100 or later. Organizations should ensure patch management processes include browser updates and enforce automatic updates where possible.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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