Skip to content
major vulnerability· requires attention

High-severity remote code execution in V8 affecting widely used Google Chrome desktop; impacts large numbers of endpoints and warrants org-wide attention.

Applications

CVE-2026-85046

HIGH
High
KEV · Exploited in wildEPSS 1%Patch availableSep 4, 2026

Type-confusion in V8 allows sandboxed arbitrary code execution via crafted HTML.

common questions

Is CVE-2026-85046 being exploited?

Yes. CVE-2026-85046 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-85046?

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

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

What does CVE-2026-85046 affect?

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

What should I do about CVE-2026-85046?

Update Chrome to 152.0.7977.82+ immediately and enforce enterprise auto-updates.

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 (prior to patch)
impact

Remote attacker can execute arbitrary code inside Chrome's renderer sandbox via a crafted HTML page, risking client compromise and data exposure.

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