Skip to main content

Google Chrome CVE-2026-78952

| EUVDEUVD-2026-65820 HIGH
Out-of-bounds Write (CWE-787)
2026-08-25 Chrome GHSA-g6pq-88qr-3vgv
8.3
CVSS 3.1 · Vendor: Chrome
Share

Severity by source

Vendor (Chrome) 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

Network vector and no-privileges reflect unauthenticated HTML delivery; high complexity captures mandatory renderer-compromise prerequisite; scope change encodes the sandbox escape to host execution.

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:N/SI:N/SA:N

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Analysis Generated
Aug 26, 2026 - 19:34 vuln.today
CVSS changed
Aug 26, 2026 - 17:23 NVD
8.3 (HIGH)
CVE Published
Aug 25, 2026 - 20:10 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 25, 2026 - 20:10 cve.org
HIGH 8.3

DescriptionCVE.org

Out of bounds write in Crashpad in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Out-of-bounds write in Chrome's Crashpad crash-reporting library on Windows, versions prior to 152.0.7977.65, enables sandbox escape and arbitrary code execution when chained with a separate renderer compromise. The flaw (CWE-787) is the second stage of a two-stage exploit: an attacker who has already gained code execution inside the sandboxed renderer can trigger the memory corruption in Crashpad to break the sandbox boundary and execute arbitrary code at Chrome process privilege on the host. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
User navigates to attacker-controlled HTML page
Delivery
Separate renderer vulnerability exploited for in-sandbox code execution
Exploit
Renderer process fully compromised
Execution
Attacker triggers crafted crash path invoking vulnerable Crashpad code
Persist
Out-of-bounds write corrupts memory outside sandbox boundary
Impact
Arbitrary code executes at Chrome process privilege on Windows host

Vulnerability AssessmentAI

Exploitation Two sequential conditions must both be satisfied: first, the attacker must have already achieved code execution inside Chrome's sandboxed renderer process on Windows via a separate, independent vulnerability not described in this CVE; second, the target must be running Google Chrome on Windows at a version prior to 152.0.7977.65. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The NVD-assigned CVSS 3.1 score of 8.3 (High) with vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H accurately reflects the chained nature of exploitation: high attack complexity captures the renderer-compromise prerequisite, scope change reflects the sandbox escape, and full C/I/A confidentiality-integrity-availability impact reflects the consequence of executing outside the sandbox. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker hosts a crafted HTML page that first exploits a separate renderer vulnerability to gain code execution inside Chrome's sandboxed renderer process on a Windows host. From that sandboxed foothold, the attacker triggers the out-of-bounds write in the Crashpad component by causing a crash-related code path to process attacker-controlled data, overwriting adjacent memory to gain control of execution flow outside the sandbox and achieving arbitrary code execution at Chrome process privilege. …
Remediation Upgrade Google Chrome on Windows to version 152.0.7977.65 or later, which constitutes the vendor-released patch per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, audit all Chrome installations across Windows systems to establish current version inventory. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-78952 vulnerability details – vuln.today

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