CVE-2026-3915
Received Received - Intake
Heap Buffer Overflow in Chrome WebML Allows Remote Memory Read

Publication date: 2026-03-11

Last updated on: 2026-03-13

Assigner: Chrome

Description
Heap buffer overflow in WebML in Google Chrome prior to 146.0.7680.71 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
2026-03-11
Last Modified
2026-03-13
Generated
2026-06-16
AI Q&A
2026-03-12
EPSS Evaluated
2026-06-15
NVD
CVE-2026-3915
EUVD
EUVD-2026-11422
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 146.0.7680.71 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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().
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

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

Impact Analysis

The vulnerability can lead to unauthorized reading of memory outside the intended buffer, which may expose sensitive information or cause the browser to behave unpredictably. Since it is classified with high severity, it poses a significant security risk when visiting malicious web pages.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-3915. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart