dbcve.org
ChromeWeb browser · Google

CVE-2026-9958

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.215 / 148.0.7778.216 or later.
See remediation →
95/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
Use after free in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially exploit heap corruption 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

Use after free vulnerability in PDFium (Google Chrome's PDF rendering engine) allows a remote attacker to potentially exploit heap corruption by serving a specially crafted PDF file. The vulnerability exists in versions prior to 148.0.7778.216.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to remediate this vulnerability.

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:< 148.0.7778.216< 148.0.7778.215

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
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 checks

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

  1. Check if Google Chrome is installed
    Open terminal and run: google-chrome --version (Linux), or check C:\Program Files\Google\Chrome\Application\chrome.exe (Windows), or check /Applications/Google Chrome.app (macOS)
    Affected if Chrome is not installed - the user is not affected by this specific Chrome vulnerability
  2. Determine the installed Chrome version
    In Chrome, navigate to chrome://version or click Help > About Google Chrome. Record the version number displayed (e.g., 148.0.7778.215)
    Affected if Version cannot be determined - assume potentially affected if Chrome is present
  3. Compare your version to the affected range
    Compare the installed version number to 148.0.7778.216. Any version lower than 148.0.7778.216 is within the affected range (both 148.0.7778.215 and versions prior are vulnerable)
    Affected if Installed version is less than 148.0.7778.216 - the user is affected by this CVE
  4. Verify PDF viewing capability is enabled
    Navigate to chrome://settings and search for 'PDF' or check if PDF files can be opened in Chrome. Also check chrome://plugins to confirm PDFium/Chrome PDF Viewer is enabled
    Affected if PDF viewing is disabled via enterprise policy or user preference - the attack surface is reduced but the vulnerable code still exists in the binary

A user is affected if Google Chrome is installed with a version lower than 148.0.7778.216 and the PDF viewing capability (PDFium) is enabled, allowing malicious PDF files to be processed.

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 148.0.7778.215 / 148.0.7778.216 or later
Fixed in 148.0.7778.215148.0.7778.216
Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later to remediate this vulnerability.

Recommended fix High confidence

Chrome 148.0.7778.216 or later

  1. Open Google Chrome
  2. Click the three-dot menu in the upper right corner
  3. Select 'Help' > 'About Google Chrome'
  4. The browser will check for updates and automatically download the latest version
  5. Click 'Restart' to apply the update after download completes
  6. Verify the version is 148.0.7778.216 or later by returning to Help > About Google Chrome

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-9958 — 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-9958 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