Skip to content
major vulnerability· requires attention

Google Chrome is ubiquitous; an RCE in Blink can affect virtually all organizations and warrants broad IT notification.

Applications

CVE-2026-19560

8.8
High
EPSS 0.39%Patch availableAug 12, 2026

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

common questions

Is CVE-2026-19560 being exploited?

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

How severe is CVE-2026-19560?

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

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

What does CVE-2026-19560 affect?

CVE-2026-19560 affects Google Chrome < 151.0.7922.137, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19560?

Update Chrome to 151.0.7922.137 or later and enforce browser updates

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.137Chromium-based browsers (potentially)
impact

Remote code execution in Chrome renderer (sandboxed) via crafted HTML; attacker can execute arbitrary code in browser context.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 151.0.7922.137

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