What is CVE-2026-102317?
Improper privilege management in Mojo in Google Chrome on on Windows prior to 154.0.8037.92 allowed a local attacker to potentially execute arbitrary code outside the sandbox via a local program. (Chromium security severity: High)
The record classifies CVE-2026-102317 under weakness class CWE-269. Its CVSS v3 base vector states that the flaw requires local access to the host, 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 48 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.6 — HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-09-29
Is CVE-2026-102317 being exploited?
No public exploitation evidence for CVE-2026-102317 is recorded in the sources Threadlinqs tracks — CISA KEV, Exploit-DB, public proof-of-concept repositories and ProjectDiscovery Nuclei — as of 2026-09-30. That is an absence of evidence in those feeds, not a guarantee that the vulnerability is unexploited.
Affected products and versions
- Google: Chrome
How to fix CVE-2026-102317
No vendor patch reference has been recorded for CVE-2026-102317 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-102317
1 tracked threat in the Threadlinqs corpus references CVE-2026-102317, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, NVD, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.