dbcve.org
ChromeWeb browser · Google

CVE-2026-6361

HIGH · 8.3 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to 147.0.7727.101 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable 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
Heap buffer overflow in PDFium in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who convinced a user to engage in specific UI gestures 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 confidence

Heap buffer overflow vulnerability in PDFium library used by Google Chrome on Windows. A remote attacker can execute arbitrary code within the Chrome sandbox by convincing a user to view a specially crafted PDF file while performing specific UI gestures. The vulnerability exists in Chrome versions prior to 147.0.7727.101.

MitigationUpdate Google Chrome to version 147.0.7727.101 or later on all Windows systems. Since the code execution is sandboxed, ensure sandbox configurations remain enabled.

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

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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 checks

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

  1. Verify Google Chrome installation on Windows
    Check for Chrome executable at common installation paths: C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. Use PowerShell command: Get-ChildItem -Path 'C:\Program Files','C:\Program Files (x86)','$env:LOCALAPPDATA\Google\Chrome\Application' -Filter 'chrome.exe' -Recurse -ErrorAction SilentlyContinue | Select-Object FullName
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or right-click chrome.exe in the installation directory and select Properties > Details to view the File Version, or run: (Get-Item 'C:\Program Files\Google\Chrome\Application\chrome.exe').VersionInfo.FileVersion
    Affected if Unable to retrieve version information from Chrome installation
  3. Compare version against affected range
    Compare your installed version number to 147.0.7727.101. Versions lower than this are within the affected range
    Affected if Installed version is less than 147.0.7727.101
  4. Confirm PDF viewing capability is enabled
    Navigate to chrome://settings in Chrome and locate the PDF settings section. By default, Chrome uses PDFium to render PDFs when opening PDF files. Verify that Chrome is configured to handle PDF content
    Affected if PDF viewing is enabled and the user opens a specially crafted PDF file

Your environment is affected if Google Chrome is installed with a version lower than 147.0.7727.101 and PDF viewing functionality is enabled.

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

Update Google Chrome to version 147.0.7727.101 or later on all Windows systems. Since the code execution is sandboxed, ensure sandbox configurations remain enabled.

Recommended fix High confidence

Chrome 147.0.7727.101 (or later)

  1. 1. Open Google Chrome on Windows
  2. 2. Click the three-dot menu icon in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click 'About Google Chrome'
  5. 5. Chrome will automatically check for updates and download version 147.0.7727.101 or later
  6. 6. Click 'Relaunch' to restart the browser and apply the update
  7. 7. After restarting, repeat steps 2-4 to confirm the version shows 147.0.7727.101
Caveat Chrome updates are generally non-breaking; ensure all tabs are saved before relaunching

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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