BaseFortify

Publication date: 2025-11-06

Last updated on: 2025-11-25

Assigner: Chrome

Description

Heap buffer overflow in Sync in Google Chrome prior to 141.0.7390.65 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: High)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-11-06

Last Modified

2025-11-25

Generated

2026-07-06

AI Q&A

2025-11-07

EPSS Evaluated

2026-07-05

NVD

CVE-2025-11458

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 141.0.7390.65 (exc)
apple	macos	*
linux	linux_kernel	*
microsoft	windows	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-122	A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CWE-787	The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

Executive Summary

This vulnerability is a heap buffer overflow in the Sync component of Google Chrome versions prior to 141.0.7390.65. It allows a remote attacker to cause an out of bounds memory read by using a specially crafted HTML page.

Impact Analysis

The vulnerability can allow a remote attacker to read memory outside the intended bounds, which could lead to exposure of sensitive information or potentially enable further exploitation of the system running the affected Chrome version.

Hi! I’m here to help you understand CVE-2025-11458. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70