Skip to content
major vulnerability· requires attention

High-severity remote code execution in Google Chrome (widely used desktop browser); patch is critical for all users and will be widely circulated in IT/security channels.

Applications

CVE-2026-85049

HIGH
High
EPSS 0.29%Patch availableSep 4, 2026

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

common questions

Is CVE-2026-85049 being exploited?

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

How severe is CVE-2026-85049?

CVE-2026-85049 is rated High. 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-85049?

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

What does CVE-2026-85049 affect?

CVE-2026-85049 affects Google Chrome (desktop) <152.0.7977.82, Chromium-based browsers using Skia. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85049?

Update Chrome to 152.0.7977.82 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 (desktop) <152.0.7977.82Chromium-based browsers using Skia
impact

Arbitrary code execution inside the Chrome sandbox via a crafted HTML page, enabling attacker-controlled code in the browser process and potential data access or further compromise.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 152.0.7977.82

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