Skip to content
major vulnerability· requires attention

Remote code execution in Google Chrome's V8 affects widely deployed browser endpoints; can lead to endpoint compromise across organizations.

Applications

CVE-2026-76038

8.8
High
EPSS 0.42%Patch availableAug 20, 2026

Type-confusion in V8 enables remote code execution in Chrome sandbox (pre-151.0.7922.169).

common questions

Is CVE-2026-76038 being exploited?

Not confirmed. CVE-2026-76038 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-76038?

CVE-2026-76038 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-76038?

Yes. A fix has been recorded for CVE-2026-76038. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76038 affect?

CVE-2026-76038 affects Google Chrome < 151.0.7922.169 (all desktop platforms). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76038?

Update Chrome to 151.0.7922.169 or later immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome < 151.0.7922.169 (all desktop platforms)
impact

Remote code execution via crafted HTML in V8, enabling sandboxed code execution and potential full host compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 151.0.7922.169

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free