ChromeWeb browser · Google
CVE-2026-2648
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 145.0.7632.109 allowed a remote attacker to perform an out of bounds memory write 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 confidenceA heap buffer overflow vulnerability exists in PDFium, the PDF rendering engine used by Google Chrome, allowing a remote attacker to perform out-of-bounds memory writes by convincing a user to open a specially crafted malicious PDF file.
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
< 145.0.7632.109CVSS 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 Google Chrome versionNavigate to chrome://version in the Chrome browser address bar and note the version number displayed, or run 'google-chrome --version' from command lineAffected if The displayed version is less than 145.0.7632.109
-
Verify Chrome channel and update statusNavigate to chrome://settings/help to see if Chrome is updated and which channel (stable, beta, etc.) is in useAffected if Chrome shows as not updated or is on an older stable channel version below 145.0.7632.109
-
Confirm PDFium is in usePDFium is built into Chrome - no separate check needed. Verify Chrome is the active browser by opening any PDF file in Chrome to confirm it uses the built-in PDF rendererAffected if Chrome is the active browser and renders PDFs using its built-in PDF viewer (this is the default behavior)
You are affected if the installed Google Chrome version is below 145.0.7632.109 and you open untrusted PDF files with Chrome's built-in PDF viewer.
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 · scoped145.0.7632.109
Update Google Chrome to version 145.0.7632.109 or later to remediate this vulnerability. Organizations should deploy the Chrome update across all affected endpoints and verify successful installation.
Chrome version 145.0.7632.109 or later (update to latest available Chrome release)
- Check your current Chrome installation version (typically via chrome://settings/help or `google-chrome --version`)
- Update your Chrome installation to version 145.0.7632.109 or later
- For Linux distributions: run your package manager update (e.g., `sudo apt update && sudo apt upgrade`, `sudo dnf update`, or `sudo yum update`)
- Restart Chrome after the update completes
- Verify the installed version is 145.0.7632.109 or higher via chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2648 — 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-2648 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