What is the CVSS score of CVE-2026-9960?

CVE-2026-9960 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by CVE-2026-9960?

Google Chrome's PDFium component contains an arbitrary code execution vulnerability affecting versions prior to 148.0.7778.216.. A patch is available.

How to fix or mitigate CVE-2026-9960?

Within 24 hours: Identify Chrome deployment scope and prepare update strategy. Within 7 days: Deploy Google Chrome version 148.0.7778.216 or later to all affected systems. Within 30 days: Verify 100% deployment coverage and monitor Chrome crash logs for exploitation indicators.

Google Chrome CVE-2026-9960

EUVD-2026-33102 HIGH

External Control of Assumed-Immutable Web Parameter (CWE-472)

2026-05-28 Chrome

GHSA-7w34-gvpm-fpjm

RCE Google

7.5

CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY

7.5 HIGH

AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

8.8 HIGH

qualitative

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 29, 2026 - 12:31 vuln.today

CVSS changed

May 29, 2026 - 12:22 NVD

7.5 (HIGH)

CVE Published

May 28, 2026 - 22:25 nvd

UNKNOWN (no severity yet)

CVE Published

May 28, 2026 - 22:25 nvd

HIGH 7.5

DescriptionCVE.org

Integer overflow in PDFium in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to execute arbitrary code inside a sandbox via a crafted font file. (Chromium security severity: High)

AnalysisAI

Sandboxed arbitrary code execution in Google Chrome's PDFium component (versions prior to 148.0.7778.216) is possible via an integer overflow triggered by a crafted font file. The flaw requires a pre-compromised renderer process and user interaction, and no public exploit identified at time of analysis, though Chromium rates it High severity.

Technical ContextAI

PDFium is the open-source PDF rendering engine integrated into Chromium-based browsers, responsible for parsing PDF documents and embedded font streams. The root cause is CWE-472 (External Control of Assumed-Immutable Web Parameter), manifesting here as an integer overflow during font file processing - arithmetic on attacker-controlled size or offset values wraps around, leading to undersized allocations or out-of-bounds memory access that the attacker can leverage for code execution. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* indicates all Chrome desktop builds below the fixed version are affected; downstream Chromium-based browsers (Edge, Brave, Opera, Vivaldi) typically inherit this bug until they roll up the patch.

RemediationAI

Vendor-released patch: Google Chrome 148.0.7778.216 - upgrade all desktop Chrome installations to this version or later via the stable channel update referenced at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html, and verify enterprise auto-update policies are not blocking the rollout. For Chromium-based browsers, apply the equivalent vendor update once available. As a compensating control where patching is delayed, disable the built-in PDF viewer via the AlwaysOpenPdfExternally enterprise policy so PDFium does not render untrusted PDFs in-process (trade-off: PDFs open in an external handler, breaking inline workflows), and consider site-isolation enforcement and strict download/file-handling policies; note these only reduce, not eliminate, exposure since this bug is reached only after a renderer is already compromised.