Skip to main content

Google Chrome CVE-2026-85052

| EUVDEUVD-2026-70703 LOW
Out-of-bounds Read (CWE-125)
2026-09-03 Chrome GHSA-5v3g-r79r-5599
3.1
CVSS 3.1 · Vendor: Chrome

Severity by source

Vendor (Chrome) PRIMARY
3.1 LOW
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
vuln.today AI
3.1 LOW

AC:H reflects mandatory renderer pre-compromise; C:L for limited sandbox-adjacent memory leak; no integrity or availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

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

Lifecycle Timeline

5
Metadata Corrected
Sep 03, 2026 - 22:40 vuln.today
tag: Buffer Overflow removed
Analysis Generated
Sep 03, 2026 - 22:16 vuln.today
CVSS changed
Sep 03, 2026 - 21:22 NVD
3.1 (LOW)
CVE Published
Sep 03, 2026 - 19:26 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 03, 2026 - 19:26 cve.org
LOW 3.1

DescriptionCVE.org

Out of bounds read in CrashReporting in Google Chrome prior to 152.0.7977.82 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Out-of-bounds memory read in Google Chrome's CrashReporting component (all versions prior to 152.0.7977.82) allows an attacker who has already compromised the renderer process to read memory beyond sandbox boundaries via a crafted HTML page, leaking limited cross-process memory contents. The exploitation chain is constrained by a hard prerequisite - renderer compromise must precede this step - placing the flaw in a post-exploitation context rather than as a standalone initial access vector. …

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
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation Exploitation requires two stacked conditions: first, the attacker must already have code execution within Chrome's renderer process (typically achieved via a separate, independent renderer RCE vulnerability); second, the target user must be interacting with a crafted HTML page that triggers the renderer compromise and subsequent crash-report manipulation. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 base score of 3.1 (Low) accurately reflects the constrained real-world impact: AC:H captures the hard prerequisite of renderer compromise, C:L reflects only partial memory disclosure, and the absence of integrity or availability impact keeps the score low. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation Update Google Chrome to version 152.0.7977.82 or later, available via Chrome's built-in update mechanism (Settings → Help → About Google Chrome) or the official stable channel release at chromereleases.googleblog.com. … Detailed patch versions, workarounds, and compensating controls in full report.

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

Share

CVE-2026-85052 vulnerability details – vuln.today

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