EM-20261030-VOGG VulnerabilityHigh severity

Google Chrome Vulnerability (CVE-2026-76029)

CVE-2026-76029

Status

Developing

Since Oct 30 01:16 UTC: signals keep joining.

First Signal: Oct 30 00:05 UTCC41 Red Hat Security Data
Page Born: Oct 30 01:16 UTCsecond source joined
Last Signal: Oct 30 01:16 UTC6 days before snapshot
Sources: 21 official · 1 research, news or crowd
Open For: 6 daysso far

Life Of This Page

1
Born

Oct 30 01:16 UTC
A second, independent source names it.
2
Developing · Now

Oct 30 01:16 UTC
New signals join; severity can move.
3
Confirmed

Not yet
CISA KEV lists it, or exploitation in the wild is reported.
4
Resolved

Not yet
Past the fix deadline and 14 days with no new signal.
5
Archived

Not yet
30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.

Vulnerability Lifecycle

Disclosed: reached

Oct 30 01:16 UTC
C6 NVD published
Scored: reached

Oct 30 01:16 UTC
CVSS 8.8 · EPSS 0.2%
Exploited: not yet

Not yet
No exploitation reported
Advisories: not yet

Not yet
None yet
Vendor Response: reached

Oct 30 00:05 UTC
C41 published
Resolved: not yet

Not yet
After 14 quiet days

Timeline

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

Signals

Oct 30 01:16 UTCCVE-2026-76029 (CVSS 8.8) (opens source in a new tab) Improper input validation in Network in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary code inside the sandbox via crafted network traffic. (Chromium security severity: High) High severityDatabaseC6 NVD CVE API 2.0
Oct 30 00:05 UTCRed Hat: CVE-2026-76029 (important) (opens source in a new tab) chromium-browser: Memory corruption in Network High severityVendorC41 Red Hat Security Data