CVE-2026-17935
Received Received - Intake

Heap Buffer Overflow in Google Chrome Codecs

Publication date: 2026-07-30

Last updated on: 2026-07-30

Assigner: Chrome

Description
Heap buffer overflow in Codecs in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Low)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-30
Last Modified
2026-07-30
Generated
2026-07-30
AI Q&A
2026-07-30
EPSS Evaluated
N/A
NVD
CVE-2026-17935
EUVD
EUVD-2026-50861

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 151.0.7922.72 (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 is a heap buffer overflow vulnerability in Google Chrome's Codecs component. It occurs when Chrome versions before 151.0.7922.72 process a specially crafted HTML page, causing memory corruption that could allow arbitrary code execution within a sandboxed environment.

Impact Analysis

An attacker could exploit this to run malicious code on your device by tricking you into visiting a specially crafted webpage. Since it executes inside a sandbox, the impact is limited but could still compromise browser security or steal data.

Mitigation Strategies

Update Google Chrome to version 151.0.7922.72 or later to address the heap buffer overflow vulnerability in Codecs.

Chat Assistant

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

EPSS Chart