CVE-2026-76029VulnerabilityPublished 30 Oct 2026

Network · Memory Corruption

Source GCVE Database

Compare

Authoritative record:CVE-2026-76029· High

Not known to be exploited : upgrade to 156.0.8078.79 soon.

Data as of 30 Oct 2026, 04:32 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 156.0.8078.79

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-72w3-57x2-f2v2

What to do

Upgrade Chrome to 156.0.8078.79.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=156.0.8078.79 <156.0.8078.79	Fixed in 156.0.8078.79

AI-suggested

A fix is available in Google Chrome version 156.0.8078.79. Users and administrators should update to this version or later to remediate the vulnerability. No additional mitigation steps are indicated.

Description

A memory corruption vulnerability exists in the Network component of Google Chrome versions prior to 156.0.8078.79. This flaw could allow a remote attacker to execute arbitrary code inside the sandbox by delivering a crafted HTML page. The issue is classified with high severity by Chromium security.

Impact

Successful exploitation could allow remote attackers to execute arbitrary code inside the sandbox of the affected Chrome browser, potentially compromising the security boundary of the browser process. This could lead to unauthorized actions or further attacks within the sandboxed environment.

Summary

CVE-2026-76029 describes a memory corruption vulnerability in the Network module of Google Chrome before version 156.0.8078.79. Exploitation requires a remote attacker to craft a malicious HTML page that triggers the flaw, potentially enabling arbitrary code execution within the browser's sandbox environment. The vulnerability is identified as CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer). No public exploit code or known in-the-wild exploitation has been reported. The vulnerability was disclosed on 2026-10-30.

CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Overflow Buffers (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Filter Failure through Buffer Overflow (opens in a new tab)
MIME Conversion (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 04:32 UTC

WeaknessesCWE-119

Technical details

References

Community reviews

Related threats