Skip to main content
CVE Vulnerability Database
Vulnerability Database/CVE-2026-79085

CVE-2026-79085: Google Chrome Authorization Bypass Vulnerability

CVE-2026-79085 is an authorization bypass flaw in Google Chrome that allows attackers with compromised renderer access to bypass web origin policy. This post explains its impact, affected versions, and mitigation steps.

Published:

CVE-2026-79085 Overview

CVE-2026-79085 is a missing authorization vulnerability in the Network component of Google Chrome prior to version 152.0.7977.65. The flaw allows a remote attacker who has already compromised the renderer process to bypass the web origin policy through a crafted HTML page. Google Chromium rates the security severity as Medium. The weakness is categorized under CWE-862: Missing Authorization.

Critical Impact

An attacker with control over a compromised renderer process can bypass same-origin protections, enabling cross-origin data access and expansion of a browser sandbox compromise.

Affected Products

  • Google Chrome Desktop versions prior to 152.0.7977.65
  • Chromium-based browsers incorporating vulnerable Network component code
  • All supported desktop platforms (Windows, macOS, Linux) running affected Chrome builds

Discovery Timeline

  • 2026-08-25 - CVE-2026-79085 published to NVD
  • 2026-08-26 - Last updated in NVD database

Technical Details for CVE-2026-79085

Vulnerability Analysis

The vulnerability resides in Chrome's Network component, which enforces authorization decisions around web origins. A remote attacker who has already achieved code execution inside the renderer process can issue crafted requests that the Network service processes without correctly validating origin authorization. The result is a bypass of the web origin policy, one of the browser's core security boundaries.

This class of flaw is typically chained with a renderer exploit. On its own it does not grant initial code execution. When paired with a renderer compromise, however, it broadens the impact by allowing the attacker to reach data and endpoints associated with origins the compromised page should not be able to touch.

Root Cause

The root cause is missing authorization enforcement [CWE-862] within the Network component. The code path handling requests originated by the renderer does not sufficiently verify that the requesting context is entitled to act on behalf of the target origin. A crafted HTML page delivered through a compromised renderer can therefore issue requests that violate the same-origin policy.

Attack Vector

Exploitation requires two conditions. First, the attacker must have already compromised the renderer process, typically through a separate memory-corruption or logic bug. Second, the attacker delivers a crafted HTML page that triggers the missing authorization path in the Network component. From that position, the attacker can read or send cross-origin data that the browser's origin model was intended to isolate. Refer to the Chromium Issue Tracker #522077127 and the Google Chrome Stable Channel Update for vendor-supplied technical detail.

Detection Methods for CVE-2026-79085

Indicators of Compromise

  • Chrome browser processes reporting versions earlier than 152.0.7977.65 in enterprise inventory data
  • Renderer processes generating unexpected outbound HTTP requests to origins unrelated to the active tab
  • Browser telemetry showing cross-origin resource access patterns inconsistent with normal user browsing

Detection Strategies

  • Inventory installed Chrome versions across managed endpoints and flag any host below 152.0.7977.65
  • Correlate endpoint process telemetry with network egress to identify renderer child processes issuing anomalous cross-origin traffic
  • Monitor for renderer process crashes or exploitation precursors that could indicate a paired renderer compromise

Monitoring Recommendations

  • Ingest browser and endpoint logs into a centralized analytics platform for version and behavior monitoring
  • Track Chrome update compliance as a recurring metric and alert on drift beyond a defined patch window
  • Watch outbound network traffic from browser processes for cross-origin request anomalies

How to Mitigate CVE-2026-79085

Immediate Actions Required

  • Update Google Chrome to version 152.0.7977.65 or later on all managed endpoints
  • Force-restart Chrome after deployment to ensure the patched binary is loaded in memory
  • Audit Chromium-based browsers and embedded WebView components for equivalent fixed versions

Patch Information

Google addressed CVE-2026-79085 in the Chrome Stable Channel release 152.0.7977.65. Administrators should follow the guidance in the Google Chrome Stable Channel Update and validate patch deployment through enterprise management tooling. Additional context is available in Chromium Issue Tracker #522077127.

Workarounds

  • No vendor-supplied workaround exists; patching to 152.0.7977.65 or later is the supported remediation
  • Reduce the practical impact by enforcing site isolation and restricting untrusted extensions that could aid renderer compromise
  • Apply enterprise policies that limit browsing to vetted sites for high-risk user populations until patching is complete

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.