ChromeWeb browser · Google
CVE-2026-6306
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 · uneditedHeap buffer overflow in PDFium in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted PDF file. (Chromium security severity: High)
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 confidenceHeap buffer overflow vulnerability in PDFium (Chrome's PDF rendering engine) allows a remote attacker to execute arbitrary code via a maliciously crafted PDF file. The vulnerability exists in versions prior to Chrome 147.0.7727.101.
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
< 147.0.7727.101CVSS 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.
-
Determine installed Google Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' in the browser menu to display the current version numberAffected if The displayed version is less than 147.0.7727.101 (e.g., 147.0.7727.100, 146.0.x.x, etc.)
-
Confirm the browser is Google ChromeCheck that the application name shown in the title bar or about page is 'Google Chrome' and not another Chromium-based browser (e.g., Microsoft Edge, Brave, Opera)Affected if The browser is Google Chrome and the version is below 147.0.7727.101
-
Verify PDFium is accessibleAttempt to open a PDF file in Chrome or navigate to chrome://pdf-internals to confirm the PDF rendering engine is availableAffected if PDF files can be rendered in Chrome and the Chrome version is below 147.0.7727.101
A user is affected if Google Chrome is installed with a version number lower than 147.0.7727.101 and the built-in PDF viewer is enabled (default state).
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.
dbcve · scoped147.0.7727.101
Update Google Chrome to version 147.0.7727.101 or later to patch the vulnerability. In enterprise environments, validate the update in a staging environment before broad deployment.
Chrome 147.0.7727.101 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Chrome will automatically check for and download the latest version
- Restart Chrome after the update completes to apply the fix
- Alternatively, download Chrome 147.0.7727.101 or later from the official Google Chrome website
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6306 — 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-2026-6306 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