ChromeWeb browser · Google
CVE-2019-5854
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 · uneditedInteger overflow in PDFium in Google Chrome prior to 76.0.3809.87 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 confidenceAn integer overflow vulnerability exists in PDFium (Google Chrome's PDF rendering engine) prior to version 76.0.3809.87. When processing a specially crafted PDF file, the integer overflow can result in heap corruption, potentially allowing a remote attacker to execute arbitrary code on the victim's system.
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
< 76.0.3809.87CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed Google Chrome versionOpen Chrome and navigate to chrome://version, or click the three-dot menu > Help > About Google Chrome. The version number is displayed at the top of the page.Affected if The version shown is less than 76.0.3809.87 (for example, 75.0.3780.100 or earlier).
-
Confirm PDF handling is enabledPDFium is Chrome's built-in PDF renderer. Verify that Chrome can open PDF files by opening any PDF in the browser. If Chrome is set to download PDFs instead of displaying them, the vulnerability may still be triggered when the user later opens the file in Chrome's PDF viewer.Affected if Chrome opens PDFs in its built-in PDF viewer (the default behavior) and the version is below 76.0.3809.87.
-
Check Chrome channel and update statusNavigate to chrome://settings/help. If Chrome is managed by an organization, check with your IT administrator to confirm whether automatic updates are enabled and which version is deployed.Affected if Chrome is on a channel or version branch that has not received the 76.0.3809.87 patch.
You are affected if Google Chrome is installed with a version lower than 76.0.3809.87 and the built-in PDF viewer is enabled (the default setting).
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 data76.0.3809.87
Update Google Chrome to version 76.0.3809.87 or later to patch the vulnerability. Organizations should deploy the update via their standard software distribution channels and verify complete coverage across managed endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5854 — 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-5854 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