# CVE-2026-84354 — Google Chrome

> As of 2026-09-08, CVE-2026-84354 is a CRITICAL-severity vulnerability in Google Chrome, CVSS v3.1 9.6, EPSS 0.4% (36.6th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-84354, most recently “Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)”.

**Last updated:** 2026-09-08

## What is CVE-2026-84354?

Incorrect authorization in FileSystem in Google Chrome prior to 152.0.7977.75 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

The record classifies CVE-2026-84354 under weakness class [CWE-863](https://intel.threadlinqs.com/cwe/CWE-863). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 79 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 9.6 — CRITICAL (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **EPSS (FIRST):** 0.4% probability of exploitation in the next 30 days, higher than 36.6% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 8.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-09-01

## Is CVE-2026-84354 being exploited?

Weaponised exploit code for CVE-2026-84354 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. It currently carries a trending score of 42 in the Threadlinqs vulnerability feed.

- [trickest/cve](https://github.com/trickest/cve/blob/main/2026/CVE-2026-84354.md) (trickest)

## Affected products and versions

- [Google](https://intel.threadlinqs.com/vendors/google): Chrome

## How to fix CVE-2026-84354

No vendor patch reference has been recorded for CVE-2026-84354 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-84354

1 tracked threat in the Threadlinqs corpus references CVE-2026-84354, either in the campaign’s CVE list or as an indicator on the campaign record.

- [Microsoft September 2026 Patch Tuesday — 999 CVEs, 3 actively exploited zero-days (CVE-2026-85880, CVE-2026-81963, CVE-2026-85046)](https://intel.threadlinqs.com/threat/TL-2026-2407) — CRITICAL · 2026-09-08

## Sources

Enriched from CVE.org, FIRST EPSS, public proof-of-concept repositories.

**Other references**

- [chromereleases.googleblog.com](https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop.html)
- [issues.chromium.org](https://issues.chromium.org/issues/498839176)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-84354
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
