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

CVE-2026-7921 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/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-7921?

Google Chrome versions prior to 148.0.7778.96 contain a remote code execution vulnerability in the Passwords component that allows attackers to execute arbitrary code on user systems through…. A patch is available.

How to fix or mitigate CVE-2026-7921?

Within 24 hours: Verify Chrome deployment baseline and enable automatic updates organization-wide. Within 7 days: Audit and confirm all Chrome installations are at version 148.0.7778.96 or later; force push update through endpoint management tools if automatic updates are insufficient. Within 30 days: Generate compliance report confirming 100% remediation of vulnerable Chrome versions and validate no installation remains below 148.0.7778.96.

Google Chrome CVE-2026-7921

EUVD-2026-27945 HIGH

Use After Free (CWE-416)

2026-05-06 Chrome

Denial Of Service Use After Free Memory Corruption RCE Google Red Hat Suse Chrome

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

SUSE

HIGH

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 06, 2026 - 22:26 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.8 (HIGH)

CVE Published

May 06, 2026 - 18:12 nvd

HIGH 8.8

DescriptionCVE.org

Use after free in Passwords in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Remote code execution in Google Chrome prior to 148.0.7778.96 enables attackers to execute arbitrary code by exploiting a use-after-free vulnerability in the Passwords component through a malicious HTML page. User interaction (visiting the crafted page) is required. CVSS score of 8.8 reflects network-based attack requiring no authentication but requiring user interaction, with high impact to confidentiality, integrity, and availability. Vendor patch available in Chrome 148.0.7778.96. No public exploitation confirmed at time of analysis.

Technical ContextAI

Use-after-free vulnerabilities (CWE-416) occur when a program continues to use a memory pointer after the referenced memory has been freed, creating a dangling pointer. In Chrome's Passwords component, this allows an attacker to manipulate freed memory through crafted HTML content, potentially gaining control of program execution flow. The vulnerability affects the password management subsystem specifically, which handles credential storage, autofill, and related browser features. The CPE identifier indicates all Chrome versions prior to 148.0.7778.96 across all platforms are affected. Chrome's security team rated this as 'High' severity, reflecting significant but not critical risk in their internal classification system.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately via the browser's built-in update mechanism (Settings > About Chrome) or through enterprise deployment tools. Chrome typically auto-updates within 24-48 hours of release, but manual checks ensure immediate protection. For enterprise environments unable to patch immediately, implement compensating controls: deploy web filtering to block known malicious domains, enforce enhanced Safe Browsing mode in Chrome policy settings (SafeBrowsingProtectionLevel=2), and disable password autofill features via Chrome Enterprise Policy (PasswordManagerEnabled=false) until patching completes, though this impacts user productivity. Organizations using Chromium-based browsers should consult vendor-specific security bulletins for equivalent patched versions. Official advisory and technical details available at http://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html and issue tracker at https://issues.chromium.org/issues/499062376.