# CVE-2026-103626 — Google Chrome

> As of 2026-10-03, CVE-2026-103626 is a CRITICAL-severity vulnerability in Google Chrome, CVSS v3.1 9.6, EPSS 0.3% (23.6th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-103626, most recently “Multiple Vulnerabilities in Google Chrome (CVE-2026-103621 through CVE-2026-103631) - GovCERT.HK A26-10-08”.

**Last updated:** 2026-10-03

## What is CVE-2026-103626?

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

The record classifies CVE-2026-103626 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 8 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.3% probability of exploitation in the next 30 days, higher than 23.6% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 7.7/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-02, last modified 2026-10-03

## Is CVE-2026-103626 being exploited?

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

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

## Affected products and versions

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

## How to fix CVE-2026-103626

Vendor advisory: [https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html](https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop.html). Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

## Threat activity tracking CVE-2026-103626

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

- [Multiple Vulnerabilities in Google Chrome (CVE-2026-103621 through CVE-2026-103631) - GovCERT.HK A26-10-08](https://intel.threadlinqs.com/threat/TL-2026-3276) — CRITICAL · 2026-10-10

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on 2026-10-10. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

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

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-103626
Full detection coverage and IOCs for threats exploiting CVE-2026-103626 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp