Skip to main content

Google Chrome EUVDEUVD-2026-27963

| CVE-2026-7930 HIGH
Improper Input Validation (CWE-20)
2026-05-06 Chrome
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious HTML with exploit cookies
  2. Delivery
    Deliver via phishing or watering-hole
  3. Exploit
    User visits attacker page
  4. Execution
    Chrome processes invalid cookie input
  5. Persist
    Trigger privilege escalation
  6. Impact
    Execute with elevated context

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V2 - Validation and Business Logic Input validation, allowlisting
Exploitation Conditions

Requires victim to navigate to attacker-controlled or compromised webpage via clicking a link, opening email attachment, or visiting a watering-hole site (CVSS UI:R). The vulnerability affects default Chrome configurations prior to version 148.0.7778.96 with no special settings required. Exploitation is limited by the need for user interaction - the attacker cannot force the victim's browser to process malicious cookies without some form of social engineering or drive-by browsing. No authentication required (PR:N), meaning any internet user running vulnerable Chrome versions can be targeted. The network attack vector (AV:N) and low complexity (AC:L) indicate exploitation is straightforward once user interaction occurs, with no dependency on timing, race conditions, or environment-specific configurations.

Impact

Real-world risk is moderate to high based on multiple factors. The CVSS vector (AV:N/AC:L/PR:N/UI:R) indicates network-based attacks with low complexity requiring no privileges but needing user interaction, making this exploitable through social engineering at scale. The 8.8 CVSS score reflects high impact across all three security properties (C:H/I:H/A:H), meaning successful exploitation grants significant control. However, the UI:R requirement substantially reduces attack surface compared to zero-click vulnerabilities. Chrome's automatic update mechanism means most users receive patches within days, limiting exposure windows. Critical missing data: EPSS exploitation probability not provided, making statistical risk assessment impossible. KEV status absent - no confirmation of active in-the-wild exploitation. POC availability unknown from provided references. SSVC technical impact would be rated high given privilege escalation, but automatable rating is partial due to UI requirement. The discrepancy between Chromium's 'Medium' internal severity and NVD's 8.8 CVSS suggests contextual factors may limit real-world impact - verify whether this requires specific user actions beyond page visit or affects only certain Chrome configurations.

Exploit ScenarioDerived

An attacker hosts a malicious webpage or injects crafted HTML into a compromised legitimate site. The page contains specially crafted cookie values that exploit Chrome's insufficient input validation. When a victim visits the page (via phishing email, malicious ad, or watering-hole attack), the browser processes the malicious cookies. Due to improper validation, the attacker's payload escalates privileges within the browser's security context, potentially enabling arbitrary code execution, cross-origin data theft, or sandbox escape. Public POC status unknown from available references.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 06, 2026

Privilege escalation in Google Chrome versions prior to 148.0.7778.96 enables remote attackers to elevate privileges through malicious HTML pages exploiting improper cookie validation. The vulnerability requires user interaction (clicking a link or visiting a malicious site) but no authentication, making it viable for phishing or watering-hole attacks. CVSS score of 8.8 indicates high severity across confidentiality, integrity, and availability. Vendor-released patch available in Chrome 148.0.7778.96 per Google's stable channel update. EPSS and KEV data not provided; exploitation status unknown at time of analysis.

RemediationAI

Upgrade immediately to Google Chrome version 148.0.7778.96 or later, as confirmed by the stable channel update advisory at http://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html. Chrome's built-in auto-update mechanism (enabled by default) delivers this patch automatically; verify installation by navigating to chrome://settings/help. For enterprise environments using managed deployments, push version 148.0.7778.96 through group policy or mobile device management. If immediate patching is not feasible, implement compensating controls: disable automatic cookie acceptance and configure Chrome to prompt for cookies on all sites via chrome://settings/cookies (note: this severely impacts usability and breaks many web applications). Block access to untrusted sites through DNS filtering or web proxies. Deploy browser isolation solutions to contain potential compromise. These workarounds provide minimal protection and should not replace patching.

Affected VersionsENISA

Chrome 148.0.7778.96 <148.0.7778.96

Affected Packages

euvd chrome fix: 148.0.7778.96

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability stems from CWE-20 (Improper Input Validation) in Chrome's cookie handling mechanism. The browser fails to properly sanitize or validate untrusted input when processing cookies, allowing specially crafted values within HTML pages to trigger privilege escalation. Modern browsers implement complex cookie policies including SameSite attributes, secure flags, and domain restrictions; insufficient validation in any of these parsing routines can enable attackers to bypass security boundaries. The CPE identifier cpe:2.3:a:google:chrome indicates the Chromium browser engine is affected. The Chromium bug tracker reference (issues/434825208) suggests this was discovered through Google's Vulnerability Reward Program or internal security review, given the Medium security severity rating assigned by the Chromium team.

Know when Chrome gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

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
Red Hat 9.6 MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
CVSS changed
May 06, 2026 - 22:22 NVD
8.8 (HIGH)
CVE Published
May 06, 2026 - 18:12 nvd
HIGH 8.8

DescriptionCVE.org

Insufficient validation of untrusted input in Cookies in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to perform privilege escalation via a crafted HTML page. (Chromium security severity: Medium)

Executive ViewAI

Why It Matters

Google Chrome versions before 148.0.7778.96 contain a privilege escalation vulnerability (CVSS 8.8) that allows attackers to gain elevated system access through malicious web pages, requiring only user interaction without authentication. This directly impacts all employees using affected Chrome versions and could enable attackers to compromise system integrity, access sensitive data, and execute unauthorized actions post-compromise.

Business Impact: High
Compensating Controls

Apply vendor patch. Until full deployment: Restrict access to untrusted websites through web filtering, enforce security awareness training emphasizing link vigilance, disable automatic updates temporarily only if you can enforce manual patching within 48 hours, and monitor Chrome process execution for abnormal privilege escalation attempts.

Threat Intelligence Overview

EPSS Score
0.1%
Top 76% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment MSRC Vendor VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

More in Chrome

View all
CVE-2015-5122 CRITICAL POC
9.8 Jul 14

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player

CVE-2016-5198 HIGH POC
8.8 Jan 19

V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac

CVE-2017-5070 HIGH POC
8.8 Oct 27

Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a

CVE-2016-1646 HIGH POC
8.8 Mar 29

The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do

CVE-2013-0758 CRITICAL POC
9.3 Jan 13

Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb

CVE-2017-5030 HIGH POC
8.8 Apr 24

Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2017-3823 HIGH POC
8.8 Feb 01

An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2015-5123 CRITICAL
9.8 Jul 14

Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13

Vendor StatusVendor

SUSE

Severity: High

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy