BaseFortify

Publication date: 2025-11-06

Last updated on: 2025-11-13

Assigner: Chrome

Description

Heap buffer overflow in WebGPU in Google Chrome prior to 141.0.7390.54 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption 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-13

Generated

2026-07-06

AI Q&A

2025-11-06

EPSS Evaluated

2026-07-05

NVD

CVE-2025-11205

Affected Vendors & Products

Vendor	Product	Version / Range
google	chrome	to 141.0.7390.54 (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 WebGPU component of Google Chrome versions prior to 141.0.7390.54. It allows a remote attacker who has already compromised the renderer process to potentially exploit heap corruption by using a specially crafted HTML page.

Impact Analysis

If exploited, this vulnerability can lead to heap corruption, which may allow an attacker to execute arbitrary code or cause a denial of service within the affected browser process. This could compromise the security and stability of your system when browsing malicious web content.

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

0/70