Chrome is a ubiquitous browser; an RCE that breaks out of the sandbox can enable broad endpoint/host compromise across organizations and requires org-wide patching.
CVE-2026-84335
Chrome auth bug allows code execution outside sandbox via crafted HTML.
Is CVE-2026-84335 being exploited?
Not confirmed. CVE-2026-84335 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.23% probability of exploitation in the next 30 days.
How severe is CVE-2026-84335?
CVE-2026-84335 is rated High with a CVSS score of 8.3. 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-84335?
Yes. A fix has been recorded for CVE-2026-84335. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-84335 affect?
CVE-2026-84335 affects Google Chrome (< 152.0.7977.75) - Desktop (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-84335?
Update Chrome to 152.0.7977.75 or later immediately; warn users about untrusted links.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can execute arbitrary code outside Chrome sandbox after compromising the renderer and leveraging social engineering, enabling host compromise.
Immediate action required
- affected< 152.0.7977.75
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.