Skip to main content

Google Chrome EUVDEUVD-2026-69748

| CVE-2026-84335 HIGH
Incorrect Authorization (CWE-863)
2026-09-02 chrome-cve-admin@google.com GHSA-7v67-mpjj-cpqj
High
Disputed · 8.3 Vendor: google
View

Attack ChainAIDerived

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

  1. Access
    Deliver crafted HTML via phishing
  2. Delivery
    Exploit separate renderer vulnerability
  3. Exploit
    Gain renderer RCE (sandboxed)
  4. Execution
    Invoke unauthorized TabStrip IPC operations
  5. Persist
    Escape renderer sandbox
  6. Impact
    Execute arbitrary code in browser process

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Two distinct preconditions must both be satisfied: (1) the attacker must have already achieved arbitrary code execution within the Chrome renderer process via a separate vulnerability - this is an explicit prerequisite stated in the description, not an assumption; (2) social engineering is required to induce the user to load a crafted HTML page (UI:R). AC:H reflects both requirements simultaneously. Exploitation is limited to desktop Chrome versions below 152.0.7977.75. Without a concurrent renderer compromise, the TabStrip authorization flaw cannot be reached from an external attacker position. Users who have already applied Chrome 152.0.7977.75 or later are not exposed.

Impact

CVSS 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) accurately reflects the high potential impact but also encodes the significant attack complexity. AC:H captures the two-stage precondition: the attacker must first independently compromise the renderer process (a separate vulnerability) and then also rely on social engineering for the TabStrip escape. EPSS data is not provided in the available intelligence; no KEV listing is present, and no public POC has been identified. Real-world exploitation probability is materially lower than the base score suggests - AC:H chained exploits require coordinated attack infrastructure and a separate unpatched renderer vulnerability. This is a meaningful vulnerability warranting prompt patching, but organizations without a concurrent unpatched renderer flaw face substantially reduced risk. The 'Authentication Bypass' tag in the input metadata is a mislabel and does not affect this assessment.

Exploit ScenarioDerived

An attacker who has already obtained renderer process execution (via a separate browser exploit) social-engineers the victim into visiting a crafted HTML page - for example, via a phishing link or malicious advertisement. The compromised renderer invokes privileged TabStrip IPC operations without proper authorization, crossing the sandbox boundary and executing attacker-controlled code in the browser process with the user's full OS privileges. No public exploit code for this specific chain has been identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Sep 02, 2026

Sandbox escape in Google Chrome's TabStrip component (versions prior to 152.0.7977.75) allows a remote attacker who has already achieved renderer process compromise to execute arbitrary code outside the Chrome sandbox via incorrect authorization in tab management IPC. The attack chain requires two conditions to be met simultaneously: a prior renderer exploit and social engineering to deliver a crafted HTML page - placing this firmly in the chained-exploit category despite the high CVSS base score. A vendor-released patch is available in Chrome 152.0.7977.75; no public exploit code or active exploitation has been identified at time of analysis.

RemediationAI

Update Google Chrome to version 152.0.7977.75 or later, which contains the vendor-released fix. Chrome's auto-update mechanism will deliver this patch to most users automatically; administrators managing enterprise deployments should verify the update via chrome://settings/help or through their endpoint management platform. The advisory at https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop.html provides the canonical release notes. As an interim compensating control, restricting access to untrusted web content or enforcing site isolation policies (--site-per-process, already default in modern Chrome) partially limits renderer compromise opportunities that feed this exploit chain, though neither eliminates the underlying vulnerability. No patch-independent workaround fully mitigates the TabStrip authorization flaw.

Affected VersionsENISA

Chrome 152.0.7977.75 <152.0.7977.75

Affected Packages

euvd chrome fix: 152.0.7977.75

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

Google Chrome isolates web content rendering in a sandboxed process (the renderer) that communicates with the privileged browser UI process via a structured IPC channel. The TabStrip component governs tab management operations in the browser UI layer and enforces authorization checks on renderer-initiated requests. CWE-863 (Incorrect Authorization) reflects a failure to verify that the requesting renderer process is entitled to invoke privileged TabStrip operations, allowing an attacker-controlled renderer to trigger actions normally restricted to the trusted browser process. The CVSS S:C (Scope Changed) metric confirms this crosses the process isolation boundary: code executing in the sandboxed renderer gains execution in the higher-privilege browser process context, effectively escaping the sandbox. The affected CPE is Google Chrome versions below 152.0.7977.75 on all supported desktop platforms.

Know when the next one hits your stack

  • 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

Sources disagree (Medium–Critical)
Vendor (google) PRIMARY 8.3 HIGH
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
vuln.today AI 8.3 HIGH

AC:H reflects the mandatory prior renderer compromise; S:C and C/I/A:H capture full sandbox escape with arbitrary code execution in the browser process.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
SUSE CRITICAL
Red Hat 8.0 MEDIUM

vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.

CVSS VectorVendor: google

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

Lifecycle Timeline

4
CVSS changed
Sep 02, 2026 - 10:22 NVD
8.3 (HIGH)
Patch available
Sep 02, 2026 - 02:01 EUVD
CVE Published
Sep 02, 2026 - 00:18 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 02, 2026 - 00:18 cve.org
HIGH 8.3

DescriptionCVE.org

Incorrect authorization in TabStrip in Google Chrome prior to 152.0.7977.75 allowed a remote attacker who had compromised the renderer process and leveraged social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Executive ViewAI

Why It Matters

Google Chrome versions prior to 152.0.7977.75 contain a sandbox escape vulnerability in the TabStrip component that permits attackers to execute arbitrary code on the system if the browser's renderer process has been previously compromised. This vulnerability is particularly relevant to organizations where users interact with untrusted web content, as exploitation requires both an initial renderer compromise and delivery of a crafted HTML page. Patching is critical to prevent post-compromise code execution that bypasses Chrome's isolation security model.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 87% exploitable
Prevalence
Ubiquitous
most widely deployed desktop browser globally, billions of installs
Data Quality
6 sources
Confidence: High

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.2%
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

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

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

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