Not on CISA's list.

Chrome and Edge: buffer overflow in V8

CVE-2026-78910 · Published 2026-08-25

How bad would it be?

8.8 out of 10

CVSS rates it high.

How likely is it to be used?

0.5%

Estimated chance of exploitation in the next 30 days, higher than 39% of all scored flaws (EPSS, 2026-10-29).

Is it already being used?

Not confirmed

It isn't on CISA's list. That doesn't prove nobody uses it: CISA only lists exploitation it has confirmed.

What the flaw is

Buffer overflow in V8 in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

From the NVD.

Fixes and advisories

chromereleases.googleblog.comVendor Advisory

Learn this

Explore this week’s weaknesses and all learning topics

Understand the kind of weakness behind this flaw. These resources teach the weakness, rather than reproduce this specific CVE. Follow the vendor's advice above to fix the affected product.

Stack buffer overflow

A write runs past a buffer on the stack and can overwrite nearby program state.

CWE-121 · NVD record: chrome-cve-admin@google.com

Video course · Free course. C programming and memory concepts are useful; covers several weakness types.

Watch the course at OpenSecurityTraining2 How it is prevented

CWE is a catalogue of weakness types. Labels come from the sources shown and can differ or change. Resource matches reviewed 16 October 2026.

On SentryFeed

Chrome and Edge: buffer overflow in V8Microsoft MSRC · 2026-10-28

Exploited flaws from CISA's KEV catalogue. Chance of exploitation from EPSS by FIRST. Descriptions and scores from the NVD. This product uses the NVD API but is not endorsed or certified by the NVD.