Skip to content
major vulnerability· requires attention

Chrome is a widely used browser; an RCE in the DOM that executes via crafted web content can affect many users and enterprise environments and warrants broad attention.

Applications

CVE-2026-76021

8.8
High
EPSS 0.45%Patch availableAug 22, 2026

Use-after-free in Chrome DOM allows remote code execution via crafted HTML.

common questions

Is CVE-2026-76021 being exploited?

Not confirmed. CVE-2026-76021 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.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-76021?

CVE-2026-76021 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-76021?

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

What does CVE-2026-76021 affect?

CVE-2026-76021 affects Google Chrome < 151.0.7922.173 (Windows/macOS/Linux), Chromium-based browsers sharing same code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76021?

Update Chrome to 151.0.7922.173 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.173 (Windows/macOS/Linux)Chromium-based browsers sharing same code
impact

Remote code execution in Chrome's DOM via crafted HTML, enabling arbitrary code execution inside the browser sandbox and potential host compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 151.0.7922.173

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